[twsocket] Issue with HTTP client POST with NTLM authentication
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
Re: [twsocket] Issue with HTTP client POST with NTLM authentication
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.comwrote: 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
Re: [twsocket] Issue with HTTP client POST with NTLM authentication
You should build the smallest possible test program, preferably using Delphi, showing it doesn't work as expected. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be - Original Message - From: Fastream Technologies ga...@fastream.com To: ICS support mailing twsocket@elists.org Sent: Thursday, November 04, 2010 6:57 PM Subject: Re: [twsocket] Issue with HTTP client POST with NTLM authentication 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.comwrote: 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 -- 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
[twsocket] Fix for THttpCli
Fix for THttpCli. Bug: If we request THttpCli.Abort in OnDocData, after abort FReceiveLen-1 (Must 0). New request (THttpCli.Get) raise exception Access violation -- 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
