More info: What our proxy server application does (which works) for basic and digest authentication is the HTTP client to call the onheaderdata and onheaderend, ..., ondocend and onrequestdone so that it can pump the 401 headers as a tunnel. It is up to the client to send the 401 negotiation requests and finally the POST data which will be pumped to target web server. As I said this works fine for basic and digest but not for NTLM--the OnRequestDone is never called.
HTH, SZ On Thu, Nov 4, 2010 at 7:45 PM, Fastream Technologies <ga...@fastream.com>wrote: > Hello, > > I could not find a demo to test this but in our application when I set > events, after the first NTLM 401 is returned the client does not fire the > OnRequestDone event! Did anybody see or test this scenario? > > Regards, > > SZ > -- 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