On 7/30/10 6:33 PM, Christopher Schultz wrote: > If all you want to do is set the character encoding, you can easily call > setCharacterEncoding and be done with it: subclassing and overriding > should not be necessary at all, otherwise nobody would have written one > of these:
No, I have other reasons to mess there. Nevertheless, adding a filter is probably less iffy, thanks for pointing that out. TC7 provides a suitable example: .../webapps/examples/WEB-INF/classes/filters/SetCharacterEncodingFilter.java > Tomcat versions before 7.x had an option in the<Connector> which could > be used to set the request URI encoding to that of the Content-Type of > the request (useBodyEncodingForURI) and another option for explicitly > and unconditionally setting the encoding to be used for URI decoding > (URIEncoding). I haven't read-up on Tomcat 7 behavior. 7.x Connector has the exact same options. I'll restate, though, that setting the Connector URIEncoding in TC7.x won't currently help when decoding GET parameters in a no-content-type case - without the filter, they will be mangled as ISO-8859-1. If this is different from previous behaviour, maybe I should report a bug. Thanks, //e
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
