Hello all, While I was trying to reproduce the presumed bug, I came across a few strange things:
http://www.fastream.com/ics/ICSHTTPPOSTBugDemo.rar (1.1MB, includes the client/server exes as well as the Delphi source code) No matter what I enter into NTLM username and password, while you are directly POSTing data in demo, it simply accepts the data! When accessed (GET) from browser it is ok. Also when I try the file upload option, even though I enter correct user credentials it always rejects! All I did was to enable NTLM authentication on the web server!! Regards, SZ On Fri, Nov 5, 2010 at 11:31 AM, Fastream Technologies <[email protected]>wrote: > Hello, > > After I started building the demo you asked for, I get an AV at the new > heartbeat function of the Web server demo. Please see the BCB project/Delphi > source code below: > > http://www.fastream.com/ics/ICSBCBWebServerDemo.rar > > I have tried to delete all the package files etc with no joy. Any idea? > > Regards, > > SZ > > > On Thu, Nov 4, 2010 at 10:57 PM, Francois PIETTE < > [email protected]> wrote: > >> You should build the smallest possible test program, preferably using >> Delphi, showing it doesn't work as expected. >> >> -- >> [email protected] >> 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" < >> [email protected]> >> To: "ICS support mailing" <[email protected]> >> 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 < >>> [email protected]>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 >>> >> >> -- >> 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
