> Notice that replacing spaces may not suffice, as it may fail too if any
> other unencoded character is included; so if you want HttpCli to handle
> it, I would suggest rather a call to an HTML-Encode function for the
> URL prior to posting the response. However, I still think that this
> should go at the point of actually sending the response, to make sure
> that *any* URL requested is encoded properly, regardless of where it
> was captured (user, redirect response, etc.).
Or allow to do it yourself at onrelocation event but as stated before that
event is constructed such that it does not allow access to the url.
So either a new event at the correct point or a automatic urldecode call to
format the url correctly.
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