[twsocket] Know the method used inside OnRequestDone?

2012-12-12 Thread Bruno Mannina

Dear ICS User,

Is exist a way to know inside the OnRequestDone if the command done was 
a POST or a GET ?


Thanks,
Bruno
--
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] Know the method used inside OnRequestDone?

2012-12-12 Thread brian -
RqType: THttpRequest;

this holds the request type, such as get, post, put, head etc.

On Wed, Dec 12, 2012 at 3:12 PM, Bruno Mannina bmann...@free.fr wrote:

 Dear ICS User,

 Is exist a way to know inside the OnRequestDone if the command done was a
 POST or a GET ?

 Thanks,
 Bruno
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto 
 http://lists.elists.org/cgi-**bin/mailman/listinfo/twsockethttp://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] Know the method used inside OnRequestDone?

2012-12-12 Thread Bruno Mannina

Hi Brian,

Great ! Thanks !

THttpRequest = (httpABORT, httpGET, httpPOST, httpPUT,
httpHEAD,  httpCLOSE);


Le 12/12/2012 16:52, brian - a écrit :

RqType: THttpRequest;

this holds the request type, such as get, post, put, head etc.

On Wed, Dec 12, 2012 at 3:12 PM, Bruno Mannina bmann...@free.fr wrote:


Dear ICS User,

Is exist a way to know inside the OnRequestDone if the command done was a
POST or a GET ?

Thanks,
Bruno
--
To unsubscribe or change your settings for TWSocket mailing list
please goto 
http://lists.elists.org/cgi-**bin/mailman/listinfo/twsockethttp://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


Re: [twsocket] Check Proxy with ICS

2012-12-12 Thread François Piette
 How can this be done? For example checking 100 proxy's at the same time
like with PHP curl_multi.
 Are there any open source projects based on ICS avaliable so I can have a
look :)

There are a lot of samples included with ICS right in the distribution. Did
you had a look at it ?
Hint: Look at OverbyteIcsHttpAsy.dproj

--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
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] Did I find a bug in THttpCli?

2012-12-12 Thread Arno Garrels
Albert Wiersch wrote:
 Hi Arno,
 
 I tested with the ICS-V7 snapshot here:
 http://wiki.overbyte.be/wiki/index.php/ICS_Download
 
 And it didn't work. It requested port 80 when it should have
 requested port 8080. It works as expected in Firefox.

Please read my previous messages in TWSocket. There are just 
two 'small' bugs:
1) property Location doesn't include the port number and
2) the Host header lacks the port number as well which is the
reason why your php script reports port 80 though the client
actually is connected to port 8080. 

The fix in standard cases ( no proxy and no SSL ) is rather simple.
However a fix that works with SSL and all proxy authentications
is not trivial since everything has to be tested carefully.
I've currently not enough spare time to fix it.

-- 
Arno  
--
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] SSLHTTPCLI Bug

2012-12-12 Thread Arno Garrels
David Loncarek wrote:
 Hello!
 
 When compiling and droping the design time component on the form in
 XE3. Compiler sadly shows this..

Define USE_SSL in your project options and *Rebuild* the project
compiling isn't enough after conditionals have changed. 

-- 
Arno
--
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] Did I find a bug in THttpCli?

2012-12-12 Thread Albert Wiersch

 Please read my previous messages in TWSocket. There are just
 two 'small' bugs:
 1) property Location doesn't include the port number and
 2) the Host header lacks the port number as well which is the
 reason why your php script reports port 80 though the client
 actually is connected to port 8080.
 
 The fix in standard cases ( no proxy and no SSL ) is rather simple.
 However a fix that works with SSL and all proxy authentications
 is not trivial since everything has to be tested carefully.
 I've currently not enough spare time to fix it.

Thanks Arno.

It's interesting that the script reports the wrong port but the connection is
made on port 8080. I suppose you had to use Wireshark to confirm that.

Do you have enough time to fix the simple stuff at least (whatever can easily
be fixed) and leave the more time consuming stuff for later? Or is it the case
that there is no simple fixes possible due to proxy and SSL issues?

Thanks,
Albert

--
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] Did I find a bug in THttpCli?

2012-12-12 Thread RTT


A quick fix that seems to correct the issue is to add a FTargetPort:= 
FPort to the procedure THttpCli.StartRelocation in the 
OverbyteIcsHttpProt unit.


procedure THttpCli.StartRelocation;
...
 CleanupSendStream;
 LoginDelayed;
 end
 else begin
+FTargetPort:= FPort;
 FCtrlSocket.OnSessionClosed := LocationSessionClosed;
 FCtrlSocket.CloseDelayed;
 end;
 end;
--
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] CookieManager?

2012-12-12 Thread Angus Robertson - Magenta Systems Ltd
 Is there a cookie manager component like in INDY?

Yes, it was added to ICS v8 earlier this year, TIcsCookies in
OverbyteIcsCookies, from the code: 

Overview


Provides a memory store for persistent and non-persistent cookies
captured from the HTTP SetCookie header, and builds a Cookie header for
any stored cookies for a URL. Persistent cookies are saved and re-read
from a simple CSV file. OverbyteIcsHttpTst1.pas shows how to handle
cookies, very few new linesa, also look at the browser demo to see how
it's used.


Angus

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