> Here I do not agree, basically the server has to provide a valid > relocation URL, anything else is a client-side workaround.
You are right. But we initially agreed that the there must be a workaround since a browse correctly handle the redirection, transparently encoding the relocation URL. > Those invalid relocation-URLs occur so rarely that automatic > reencoding or even a full validation in most cases was nothing but > wasted performance. And if we would build in a simple and fast > auto-encoding today I bet that another user will get another kind > of invalid URL tomorrow. Wel, probably. > Instead the component should provide access to parts of a URL, > either by var-parameters in event OnLocationChange or by public > properties so the application developer can do what's required himself. OK, but as DZ said, it must ne delivered at correct time. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Saturday, April 21, 2007 1:35 PM Subject: Re: [twsocket] httpcli v6 "bad request" > Francois PIETTE wrote: >>> If you think -- like me -- that it is the >>> responsibility of the application developer to >>> properly encode URLs, and not the component, then the >>> solution for those applications that require the >>> IE-like behaviour is for the developer to call >>> UrlEncode himself at the application level, >> >> I agree. > > How shall the application developer currently do that? > >> >>> and to not use FollowRedirect, but to handle redirections >>> himself and properly encode URLs. >> >> There I don't agree. If the component do automatic relocation, then >> it must take appropriate action to encode URL. > > Here I do not agree, basically the server has to provide a valid > relocation URL, anything else is a client-side workaround. > Those invalid relocation-URLs occur so rarely that automatic > reencoding or even a full validation in most cases was nothing but > wasted performance. And if we would build in a simple and fast > auto-encoding today I bet that another user will get another kind > of invalid URL tomorrow. > > Instead the component should provide access to parts of a URL, > either by var-parameters in event OnLocationChange or by public > properties so the application developer can do what's required himself. > A class TIcsUrl could help to make current source code better readable. > A faster and more copmlete function UrlEncode should be made available. > > > -- > Arno Garrels [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 -- 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
