Ah, ok. But how does NTLM works with HTTP/1.0 then? Is it 1.1 only? What should we do if the server admin specifies NTLM but the client does not support HTTP/1.1? Is this a rare situation?
Best Regards, SZ ----- Original Message ----- From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Thursday, September 14, 2006 3:57 PM Subject: Re: [twsocket] Fw: Urgent (Another simple NTLM question) > NTLM requires Keep-Alive, but the server sends "Connection: close" in > the header of 401Answer. > > Fastream Technologies wrote: >> Here it is: http://www.fastream.com/ics/ntlm.pcap >> >> Regards, >> >> SZ >> >> ----- Original Message ----- >> From: "Arno Garrels" <[EMAIL PROTECTED]> >> To: "ICS support mailing" <twsocket@elists.org> >> Sent: Thursday, September 14, 2006 3:36 PM >> Subject: Re: [twsocket] Fw: Urgent (Another simple NTLM question) >> >> >>> Fastream Technologies wrote: >>>> Basicallly the ntlmmessage = NULL where it must not be--ethereal >>>> calls this >>>> malformed header!!! >>> >>> Please, please, please upload the Ethereal dump in as a *.pcap file >>> somewhere so we can open it with ethereal. >>> >>> -- >>> To unsubscribe or change your settings for TWSocket mailing list >>> please goto http://www.elists.org/mailman/listinfo/twsocket >>> Visit our website at http://www.overbyte.be > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
