aboutsummaryrefslogtreecommitdiff
path: root/tests/data/test162
AgeCommit message (Collapse)Author
2006-04-05Michele Bini modified the NTLM code to work for his "weird IIS case"Daniel Stenberg
(http://curl.haxx.se/mail/lib-2006-02/0154.html) by adding the NTLM hash function in addition to the LM one and making some other adjustments in the order the different parts of the data block are sent in the Type-2 reply. Inspiration for this work was taken from the Firefox NTLM implementation. I edited the existing 21(!) NTLM test cases to run fine with these news. Due to the fact that we now properly include the host name in the Type-2 message the test cases now only compare parts of that chunk.
2005-05-11Modified the default HTTP headers used by libcurl:Daniel Stenberg
A) Normal non-proxy HTTP: - no more "Pragma: no-cache" (this only makes sense to proxies) B) Non-CONNECT HTTP request over proxy: - "Pragma: no-cache" is used (like before) - "Proxy-Connection: Keep-alive" (for older style 1.0-proxies) C) CONNECT HTTP request over proxy: - "Host: [name]:[port]" - "Proxy-Connection: Keep-alive"
2005-03-21Make NTLM tests depend on the NTLM feature at not SSL, since the NTLM supportDaniel Stenberg
is no longer only present when built with SSL support.
2005-01-25A minor "syntax error" in numerous test files correctedDaniel Stenberg
2004-11-29stricter newline policyDaniel Stenberg
2004-09-08Now the test servers and test cases can run on a custom port number. There'sDaniel Stenberg
no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script.
2004-04-23require SSL as otherwise NTLM doesn't work!Daniel Stenberg
2004-04-22- David Byron found and fixed a small bug with the --fail and authenticationDaniel Stenberg
stuff added a few weeks ago. Turns out that if you specify --proxy-ntlm and communicate with a proxy that requires basic authentication, the proxy properly returns a 407, but the failure detection code doesn't realize it should give up, so curl returns with exit code 0. Test case 162 verifies this.