Re: [twsocket] Found the cause of the issue for 10053 errors in HTTP

2011-05-11 Thread Fastream Technologies 
I am 99% sure that there is a problem with HTTPS POST. I have posted code
here many times before but unfortunately nobody said anything. Both client
and server are ICS. It works fine with HTTP.

Regards,

SZ

On Wed, May 11, 2011 at 13:29, Arno Garrels  wrote:

> Fastream Technologies wrote:
> > Hello,
> >
> > In some cases SetReady() (hence OnRequestDone) is called twice, where
> > the second one should not be called and interferes with following
> > HTTP request (if any), ruining the state machine. I suggest something
> > like:
> >
> > void __fastcall SetReady()
> > {
> > if(alreadySetReady)
> >  return;
> > alreadySetReady = true;
> > ...
> > }
> >
> //---
>
> Such a fix won't fix the cause of the problem.
> Also don't you use a custom OverbyteIcsHttpProt.pas?
>
> This fix from SVN rev. #623 springs to mind:
>
> procedure THttpCli.Abort;
> var
>bFlag : Boolean;
>Msg   : TMessage;
> begin
>FLocationFlag := FALSE;  { Do not follow relocations V7.10 }
>{ The following two lines prevent OnRequestDone from trigger twice V7.10
> }
>FRcvdCount:= 0;  { Clear the receive buffer V7.10 }
>FReceiveLen   := 0;  { Clear the receive buffer V7.10 }
> [..]
>
> --
> 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
>
--
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] Found the cause of the issue for 10053 errors in HTTP

2011-05-11 Thread Arno Garrels 
Fastream Technologies wrote:
> Hello,
> 
> In some cases SetReady() (hence OnRequestDone) is called twice, where
> the second one should not be called and interferes with following
> HTTP request (if any), ruining the state machine. I suggest something
> like: 
> 
> void __fastcall SetReady()
> {
> if(alreadySetReady)
>  return;
> alreadySetReady = true;
> ...
> }
> //---

Such a fix won't fix the cause of the problem.
Also don't you use a custom OverbyteIcsHttpProt.pas?
 
This fix from SVN rev. #623 springs to mind: 

procedure THttpCli.Abort;
var
bFlag : Boolean;
Msg   : TMessage;
begin
FLocationFlag := FALSE;  { Do not follow relocations V7.10 }
{ The following two lines prevent OnRequestDone from trigger twice V7.10 }
FRcvdCount:= 0;  { Clear the receive buffer V7.10 }
FReceiveLen   := 0;  { Clear the receive buffer V7.10 }
[..]

-- 
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

[twsocket] Found the cause of the issue for 10053 errors in HTTP

2011-05-11 Thread Fastream Technologies 
Hello,

In some cases SetReady() (hence OnRequestDone) is called twice, where the
second one should not be called and interferes with following HTTP request
(if any), ruining the state machine. I suggest something like:

void __fastcall SetReady()
{
 if(alreadySetReady)
  return;
 alreadySetReady = true;
 ...
}
//---
To be added to HTTP client component code.
Best 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