Adding a filter by default is not strictly a good thing. If your character set output is UTF-8 then setting the request charset to UTF-8 is the right thing. However, if your encoding isn't UTF-8, you run the risk of corrupting your output when the browser reads the content as UTF-8 when it's actually something else.
There is a lot of alignment with ASCII and UTF-8, however it's not perfect in all cases. I've run across subtle bugs were UTF-8 parsers aren't able to understand some extended ASCII characters. Problems like these are hard enough to track down when the framework isn't incorrectly setting content type for you. What's the problem with properly setting charset in the page markup? The approach also scales to sites that have multiple charsets. The given filter would need to be extended to support charset/URI matching in order to support that case. I suppose if I don't like it I don't have to use the filter. Just be aware that subtle tolls live under this bridge. Don't use without thinking. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953019#3953019 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953019 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
