e" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Monday, September 04, 2006 9:36 AM
> Subject: Re: [twsocket] Solution to problem with THttpCli
>
>
> :> I set a flag in THttpCli:OnDocBegin and reset it in OnDocEnd. If it is
> not
> : &g
ocket) and seems not bad now. You can check it out here:
http://www.fastream.com/iqreverseproxy.php.
Best Regards,
SZ
- Original Message -
From: "Francois Piette" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Monday, September 04, 2006 9:36 AM
Subject: Re:
> I set a flag in THttpCli:OnDocBegin and reset it in OnDocEnd. If it is not
> reset in OnRequestDone, then there was an error. Simple, isn't it?
Is Abort the error cause ?
Just adding a flag doesn't change anything. What does the component in case
of error ?
It isn't clear to me that there is a b
ot;
Sent: Sunday, September 03, 2006 5:29 PM
Subject: Re: [twsocket] Solution to problem with THttpCli
: Could you show the actual changes you made in the component ?
: --
: [EMAIL PROTECTED]
: http://www.overbyte.be
:
: - Original Message -
: From: "Fastream Technologies&quo
Could you show the actual changes you made in the component ?
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Fastream Technologies" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, September 03, 2006 1:35 PM
Subject: [tws
Hello,
I found the solution to when to abort THttpCli connections by setting a
clientError flag in the beginning and then resetting it in OnDocEnd.
Sometimes when the browser is refreshed too quickly, our reverse proxy was
not calling OnDocEnd yet the OnRequestDone was called WITHOUT an error c
