On Thu, 18 Dec 2003, David Byron wrote:

> When broken, it contains:
>
> New client connected
> Wrote request input to log/server.input
> Got request: GET /91 HTTP/1.1
> Found test number 91 in path
> Received request, now send response number 91 part 0
> Fetch response data, test 91 part 0
> connection close instruction swsclose found in response
> Response sent!
> instructed to close connection after server-reply
> Closing client connection
>
> When working, it starts the same, but continues with
>
> New client connected
> Wrote request input to log/server.input
> Got request: GET /91 HTTP/1.1
> Found test number 91 in path
> Received NTLM type-1, sending back data 1001

Ah. Ignore my previous reply, it was premature and wrong. I re-read your mail
and I see I misunderstood it.

The fact that the NTLM type-1 request doesn't always come after the first
response is sent is rather an indication that libcurl doesn't do right. The
first response tells libcurl about three different authentication methods
available, and it is then supposed to pick NTLM from those three and continue
with that.

Obviously it doesn't do this always! :-/

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
   [[ Do not send mails to this email address. They won't reach me. ]]
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click