Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2012-01-20 Thread Arno Garrels
RTT wrote: Why this fix has not been added? Thanks, I just checked in your change untested, rev. #866 Available via SVN now or included in the next nightly snapshot ZIP. http://wiki.overbyte.be/wiki/index.php/ICS_Download -- Arno Garrels -- To unsubscribe or change your settings for TWSocket

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2012-01-19 Thread RTT
Why this fix has not been added? The first one is not really important, even if completes the logic already taken by the ParseURL for URLs missing the protocol , but the second change, used by the THttpCli when parsing redirection URLs, is IMO mandatory, because URLs beginning with '//' are

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2012-01-19 Thread Arno Garrels
RTT wrote: Why this fix has not been added? AFAIR Francois wasn't convinced, if there are no side effects and Francois doesn't refuse it explicitly I'll add it. -- Arno Garrels The first one is not really important, even if completes the logic already taken by the ParseURL for URLs missing

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-28 Thread RTT
RFC2616 references RFC2396 as a source of information about URI in the description of a general syntax (Chapter 3.2.1). Then the next chapter (3.2.2) specifies the http URL which /must/ start with the http: scheme. The RFC2396 also don't say noting about a default protocol for such

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-27 Thread Arno Garrels
RTT wrote: The bellow provided example isn't producing anymore the relocation with such begin with // address, but this don't invalidate the fact that the THTTPCli cant resolve a url such as: //www.google.com nor handle a relocation with the location field set to equal URL I haven't

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-27 Thread Francois PIETTE
According to the rfc1808.txt, an URL can start with // The ParseURL function will fail in such cases. Also, during a relocation, the THTTPCli fail to parse a location field with such URLs. Here is an example, that result in a relocation with these characteristics

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-27 Thread RTT
On 27-10-2011 19:28, Francois PIETTE wrote: If I'm wrong, please point me to the exact text in the /HTTP/ standard (RFC2616). From RFC2396, that merge RFC1808 with two others, and that is referenced in the RFC2616.

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-27 Thread RTT
On 27-10-2011 18:33, Arno Garrels wrote: I'd be happy to see more contributions from the ICS users in general. 1st change In unit OverbyteIcsUrl, procedure ParseURL(..., replace if (url[1] = '/') then begin

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-27 Thread Francois PIETTE
of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -Message d'origine- From: RTT Sent: Thursday, October 27, 2011 9:01 PM To: ICS support mailing Subject: Re: [twsocket] THTTPCli fail to resolve URLs that start

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-27 Thread Francois PIETTE
support mailing Subject: Re: [twsocket] THTTPCli fail to resolve URLs that start with // On 27-10-2011 18:33, Arno Garrels wrote: I'd be happy to see more contributions from the ICS users in general. 1st change In unit

Re: [twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-26 Thread RTT
The bellow provided example isn't producing anymore the relocation with such begin with // address, but this don't invalidate the fact that the THTTPCli cant resolve a url such as: //www.google.com nor handle a relocation with the location field set to equal URL According to the