Hello:
Wouldn't it be more appropriate for the application to guarantee that
the URL conforms to RFC 1738 by encoding all illegal characters
(including spaces)? Common client applications (browsers) do this
automatically for the user, but it is still stupid for the server to
redirect you to an invalid URL, no?
dZ.
On Apr 18, 2007, at 12:49, Frans van Daalen wrote:
> The website and page that is the cause of this problem is rather hard
> to get
> to. I'm trying to create a simial problem on one of the website I have
> myself. As soon as I have done that I will let you know.
>
> I have solved it for now by with
>
> httpClient.FPath := stringreplace(httpclient.fpath,'
> ','%20',[rfreplaceall]);
>
--
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
