mirror of
https://github.com/curl/curl.git
synced 2026-04-13 12:41:42 +08:00
a87383828e
There remain some false positives, hits in test data, and `dir` use, around 100 issues in total. There is no plan to enforce badwords on tests. Also: - badwords.txt: let a few `manpage[s]` occurrences through (in Perl code). Closes #19541
61 lines
1.2 KiB
Plaintext
61 lines
1.2 KiB
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
HTTP
|
|
HTTP GET
|
|
HTTP proxy
|
|
HTTP proxy NTLM auth
|
|
FAILURE
|
|
</keywords>
|
|
</info>
|
|
|
|
# Server-side
|
|
<reply>
|
|
<data1001 nocheck="yes">
|
|
HTTP/1.0 407 BAD BOY
|
|
Proxy-Authenticate: Basic realm="Squid proxy-caching web server"
|
|
Server: swsclose
|
|
Content-Type: text/html
|
|
|
|
Even though it is the response code that triggers authentication, we are
|
|
using NTLM and the server is not, so we should fail. We know the server
|
|
is not because there is no Proxy-Authorization: NTLM header
|
|
</data1001>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<features>
|
|
NTLM
|
|
SSL
|
|
!SSPI
|
|
proxy
|
|
</features>
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
HTTP GET asking for --proxy-ntlm when some other authentication is required
|
|
</name>
|
|
<command>
|
|
http://%HOSTIP:%HTTPPORT/%TESTNUMBER --proxy http://%HOSTIP:%HTTPPORT --proxy-user foo:bar --proxy-ntlm --fail
|
|
</command>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<protocol crlf="headers">
|
|
GET http://%HOSTIP:%HTTPPORT/%TESTNUMBER HTTP/1.1
|
|
Host: %HOSTIP:%HTTPPORT
|
|
Proxy-Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
|
|
User-Agent: curl/%VERSION
|
|
Accept: */*
|
|
Proxy-Connection: Keep-Alive
|
|
|
|
</protocol>
|
|
<errorcode>
|
|
22
|
|
</errorcode>
|
|
</verify>
|
|
</testcase>
|