5 Commits

Author	SHA1	Message	Date
Daniel Stenberg	da58d03ff7	Venkat Akella found out that libcurl did not like HTTP responses that simply ... responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring.	2006-11-25 13:32:04 +00:00
Daniel Stenberg	2bd3033f68	NTLM2 session response support	2006-06-07 14:14:04 +00:00
Daniel Stenberg	b0adcd6a46	cut off a bit more of the type-2 ntlm message since it differs between ... hosts	2006-04-05 12:46:03 +00:00
Daniel Stenberg	be285cde3f	Michele Bini modified the NTLM code to work for his "weird IIS case" ... (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.	2006-04-05 12:35:48 +00:00
Daniel Stenberg	c0d343d56d	do a POST with NTLM and add two custom headers	2005-08-11 21:33:40 +00:00