-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 nch,
nch wrote: | I have a form that has an input field named "query". I type "piraña" | an submit the form using the GET method. I can see the browser has | encoded this parameter into the URI as query=pira%C3%B1a Is this a correct UTF-8 encoding of the parameter? I don't have my unicode conversion chart handy right now. | I set a breakpoint Stop right there. If you are executing TC through a debugger, are you sure that it is using its standard server.xml configuration? | into the filter so when the request hits the filter I can see | getCharacterEncoding() returns null. The filters sets it to "UTF-8". FYI, this has no bearing on the interpretation of the URI. | Then the request gets to the controller where I can see the request | parameter "query" is set to "piraña". Just in case it doesn't go through email very well, I see "pir" followed by an A with a tilde over it, followed by a +/- symbol, followed by an "a". Definitely not right. Is that what you'd expect if you improperly interpreted the UTF-8, URL-encoded "piraña" as if it were ISO-8859-1? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhZRO8ACgkQ9CaO5/Lv0PBXBQCeP3YKqnpJDO65N8lfvO9ThPhr Nr8AnRbPC1BxIEOXqIOrMCS1ACy7YFU6 =y8/w -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
