DO NOT REPLY [Bug 25526] - tomcat parses the query string parameters as iso-8859-1

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=25526>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=25526

tomcat parses the query string parameters as iso-8859-1





------- Additional Comments From anton@atlassian.com  2004-07-09 02:03 -------
Sorry - but I am still confused: in your comment, in point number 1 you say that
there is useBodyEncodingForURI parameter for Cayote that for TC4 defaults to true. 

In the second point you say that Cayote has URIEncoding parameter which is set
to ISO-8859-1 and in the third point you mention that the URIEncoding parameter
is used to parse the URL parameters (by default).

>From you points I do not understand what is the purpose of the
useBodyEncodingForURI and when is it used by Tomcat?

In TC4, the behaviour that we are seeing is that the URL parameters are parsed
using ISO-8859-1 even of the request.setCharacterEncoding() is called with "UTF-8".

Is there a way to configure Tomcat 4 and 5 (hopefully without calling
Tomcat/Cayote specific methods on objects at runtime) which will force the URL
Parameters to be parsed using the encoding of the body?

The reason I am after this, is that sometimes there is a need to send a browser
redirect passing parameters. A redirect always results in a GET HTTP request
from the browser. I would prefer not to use the session to store the parameters.

Thanks for all your help and information!

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org