| xf.li | 6c8fc1e | 2023-08-12 00:11:09 -0700 | [diff] [blame] | 1 | <testcase> |
| 2 | <info> |
| 3 | <keywords> |
| 4 | HTTP |
| 5 | HTTP GET |
| 6 | HTTP proxy |
| 7 | HTTP proxy NTLM auth |
| 8 | FAILURE |
| 9 | </keywords> |
| 10 | </info> |
| 11 | |
| 12 | # Server-side |
| 13 | <reply> |
| 14 | <data1001 nocheck="yes"> |
| 15 | HTTP/1.0 407 BAD BOY |
| 16 | Proxy-Authenticate: Basic realm="Squid proxy-caching web server" |
| 17 | Server: swsclose |
| 18 | Content-Type: text/html |
| 19 | |
| 20 | Even though it's the response code that triggers authentication, we're |
| 21 | using NTLM and the server isn't, so we should fail. We know the server |
| 22 | isn't because there's no Proxy-Authorization: NTLM header |
| 23 | </data1001> |
| 24 | </reply> |
| 25 | |
| 26 | # Client-side |
| 27 | <client> |
| 28 | <features> |
| 29 | NTLM |
| 30 | SSL |
| 31 | !SSPI |
| 32 | proxy |
| 33 | </features> |
| 34 | <server> |
| 35 | http |
| 36 | </server> |
| 37 | <name> |
| 38 | HTTP GET asking for --proxy-ntlm when some other authentication is required |
| 39 | </name> |
| 40 | <command> |
| 41 | http://%HOSTIP:%HTTPPORT/%TESTNUMBER --proxy http://%HOSTIP:%HTTPPORT --proxy-user foo:bar --proxy-ntlm --fail |
| 42 | </command> |
| 43 | </client> |
| 44 | |
| 45 | # Verify data after the test has been "shot" |
| 46 | <verify> |
| 47 | <protocol> |
| 48 | GET http://%HOSTIP:%HTTPPORT/%TESTNUMBER HTTP/1.1
|
| 49 | Host: %HOSTIP:%HTTPPORT
|
| 50 | Proxy-Authorization: NTLM TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
|
| 51 | User-Agent: curl/%VERSION
|
| 52 | Accept: */*
|
| 53 | Proxy-Connection: Keep-Alive
|
| 54 |
|
| 55 | </protocol> |
| 56 | <errorcode> |
| 57 | 22 |
| 58 | </errorcode> |
| 59 | </verify> |
| 60 | </testcase> |