[twsocket] 10053 error occurring only on Win2008 (SP2) and not on Win7

2010-12-24 Thread Fastream Technologies
Hello, With the HttpCli, I get 10053 when lots of consecutive POSTs are made with SSL. I first thought it is related to the 4096 bit self-signed cert we used but it does not happen on Win2008. The test machine is remote (in the Netherlands) and when I run the GUI (web client) from here on my Win7,

Re: [twsocket] HttpCli / Async in thread problems --- Tryng to trace

2010-12-24 Thread Frans van Daalen
You are right, I did not test the GetAsync, in async mode RequestDone is actually fired with StatusCode 0 after relocation. Triggered by a call to CheckDelaySetReady in GetBodyLineNext. When I add a check for FLocationFlag there it _SEEMS_ to fix it, has to be still tested very hard in order n

Re: [twsocket] Season's greetings

2010-12-24 Thread Xavier Mor-Mur
Thanks Francois and my best greetings and wishes to all people around the world. Bon Nadal i joiós 2011 Feliz Navidad y venturoso 2011 Xavi Al 23/12/2010 21:49, En/na Francois PIETTE ha escrit: Hi Everyone ! Happy Holidays and best wishes for 2011 ! Merry Christmas, -- francois.pie...@overb

Re: [twsocket] HttpCli / Async in thread problems --- Tryng to trace

2010-12-24 Thread Fastream Technologies
What will happen if we want no-follow-relocation and just need to pump the 301/302/307 headers? Regards, SZ On Fri, Dec 24, 2010 at 3:37 PM, Arno Garrels wrote: > Arno Garrels wrote: > > Arno Garrels wrote: > >> Frans van Daalen wrote: > Frans van Daalen wrote: > > seems that the bug

Re: [twsocket] HttpCli / Async in thread problems --- Tryng to trace

2010-12-24 Thread Arno Garrels
Arno Garrels wrote: > Arno Garrels wrote: >> Frans van Daalen wrote: Frans van Daalen wrote: > seems that the bug is also somewhere related to the NTLM code or > call because the icslogger shows the following > > - Starting relocation process > - state = httpReady > -

Re: [twsocket] HttpCli / Async in thread problems --- Tryng to trace

2010-12-24 Thread Arno Garrels
Arno Garrels wrote: > Frans van Daalen wrote: >>> Frans van Daalen wrote: seems that the bug is also somewhere related to the NTLM code or call because the icslogger shows the following - Starting relocation process - state = httpReady - PrepareNTLM - Prepare

Re: [twsocket] HttpCli / Async in thread problems --- Tryng to trace

2010-12-24 Thread Arno Garrels
Frans van Daalen wrote: >> Frans van Daalen wrote: >>> seems that the bug is also somewhere related to the NTLM code or >>> call because the icslogger shows the following >>> >>> - Starting relocation process >>> - state = httpReady >>> - PrepareNTLM >>> - PrepareNTLM >>> - RequestDone

Re: [twsocket] HttpCli / Async in thread problems --- Tryng to trace

2010-12-24 Thread Frans van Daalen
Frans van Daalen wrote: seems that the bug is also somewhere related to the NTLM code or call because the icslogger shows the following - Starting relocation process - state = httpReady - PrepareNTLM - PrepareNTLM - RequestDone

Re: [twsocket] HttpCli / Async in thread problems --- Tryng to trace

2010-12-24 Thread Arno Garrels
Frans van Daalen wrote: > > Found an error in OverbyeIcsHttpProt, not the reason for the error > above > > line 1760 : > DebugLog(loProtSpecDump, Format('PrepareNTLMAuth end, FStatusCode = > %d ' + > > should be > > DebugLog(loProtSpecDump, Format('PrepareNTLMAuth Begin, FStatusCode = > %d '

Re: [twsocket] HttpCli / Async in thread problems --- Tryng to trace

2010-12-24 Thread Arno Garrels
Frans van Daalen wrote: > seems that the bug is also somewhere related to the NTLM code or call > because the icslogger shows the following > > - Starting relocation process > - state = httpReady > - PrepareNTLM > - PrepareNTLM > - RequestDone