Arno Garrels wrote:
> Fastream Technologies wrote:
>> In my case, I get data from first head being pending in second
>> head/GET. I know it is weird/rare case yet this customer was annoyed
>> and he led us to panic even more...
This sounds like value of FReceiveLen is not always zero when you do
the next request. In V7 I added the workaround below when I hit a
similiar problem with a strange proxy server, please try:
procedure THttpCli.SocketSessionClosed(Sender: TObject; ErrCode: Word);
begin
{$IFNDEF NO_DEBUG_LOG}
if CheckLogOptions(loProtSpecInfo) then { V1.91 } { replaces $IFDEF
DEBUG_OUTPUT }
DebugLog(loProtSpecInfo, 'SessionClosed Error: ' +
IntToStr(ErrCode));
{$ENDIF}
=> FReceiveLen := 0; { AG 11 Jan 2009 always clear the
buffer! }
This might be not enough though.
--
Arno Garrels
--
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
