https://issues.apache.org/bugzilla/show_bug.cgi?id=49464
Summary: DefaultServlet and CharacterEncoding
Product: Tomcat 6
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: felix.schumac...@internetallee.de
DefaultServlet doesn't set a character encoding. As per spec the encoding of
the page is asssumed to be iso-8859-1.
If files are served with a different encoding, this can lead to display
problems in the browser.
The problem has been discussed in
http://old.nabble.com/DefaultServlet-doesn%27t-set-charset-td18893115.html#a18929527
In http://marc.info/?l=tomcat-user&m=127678462332564&w=2 another component was
added - namely mod_jk/httpd - which set a character encoding on its own, if no
character set was set previously.
There are at least three different solutions for this problem.
One of them is extending DefaultServlet to be configurable to include a charset
in the response. A patch has been proposed by Markus Schönhaber (MKS) and can
be found at
http://www.ddt-consult.de/sendCharset.patch
The two other solutions which were discussed are
* configure httpd/mod_jk properly by adding AddDefaultCharset ENCODING to the
right location/host
* Use a filter to set the character encoding
All in all I still think it would be a good idea to explicitly set the wanted
encoding in the first possible place, which is the DefaultServlet.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
