Hi -
This may be irrelevant to the original asker by now, and I'm working with Tomcat 7, but in case it's of use: Christopher Schultz, Wed, 21 Apr 2010 08:43:57 -0700 wrote:
The filter cannot influence the way that GET parameters are decoded. The only way to change that is to set URIEncoding="UTF-8" on your <Connector> in server.xml.
This is, at least in some special cases, incorrect: based on quite a bit of Tomcat 7.0b embedding effort recently, I tracked this same issue all the way through, and Tomcat defaults to ISO-8859-1 if the request does not specify content-type explicitly, despite whatever Connector settings. See e.g. CoyoteAdapter.parsePathParameters() for an example. (A request without content-type happens e.g. in Firefox 3.6 with a dynamically created script DOM element to an external URL; I'm sure there are other occasions as well.) The only way I found around it was to have my own Connector implementation provide my own Request wrapper, and override getCharacterEncoding() there based on the URIEncoding setting. (Not very user-friendly; I imagine it's doable with the standard configuration scheme, but I can't help with that - sorry. Feel free to email if you need pointers, anyway.) Cheers, //e
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
