| <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's the response code that triggers authentication, we're | |
| using NTLM and the server isn't, so we should fail. We know the server | |
| isn't because there's 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> | |
| 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> |