On Fri, Sep 19, 2008 at 7:45 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >------- Original Message ------- > >From : Maurizio > Lotauro[mailto:[EMAIL PROTECTED] > >Sent : 9/19/2008 11:24:14 AM > >To : twsocket@elists.org > >Cc : > >Subject : RE: Re: [twsocket] Early web server response > > > > This will work with Basic bu not with NTLM because > (IIRC) > > the authentication phase is started by the server > with the > > first 401. > > > > Is there a way to empty the socket buffer? > > Again, I must be missing something (I admit I am not > very familiar with NTLM authentication). So the > server sends a 401 error response, your client > detects this right after sending the header, while in > the process of sending the body. It then reacts > immediately by terminating the connection. It then > re-connects and responds to the 401 response with a > new request which includes the authentication header. > > How is this different than the normal way: You send > your request completely (head and body), the server > responds with a 401 error response and closes the > connection (or you close the connection). You then > re-connect and perform the request again with the > authentication header. > > -dZ. > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be > What you miss is NTLM 401 response includes some random data that must be returned with the request in the same connection. Otherwise value would be lost at server side!! -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
