-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thierry,
On 5/2/2011 4:31 AM, Thierry Templier wrote:
> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"></meta>
Just to be sure, I highly recommend coding your pages like this:
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=<?=
response.getCharacterEncoding() %>"></meta>
This will ensure that you aren't sending ISO-8859-1 but claiming that
it's UTF-8.
> The content type header is the same and specifies UTF-8 as encoding... However it appears
that when using Apache / modjk / Tomcat, the reponse content is compressed using gzip. It's
not the case when directly accessing Tomcat. I don't know if it could be the reason of the
problem...
gzip encoding is unlikely to be causing the problem.
Can you post the configuration you have for your <Connector> elements in
Tomcat's conf/server.xml? Remember to remove any sensitive information
(ip addresses, JK secrets, etc.)
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2+vrEACgkQ9CaO5/Lv0PBqIgCeKKh2ihG6UX/EESHe1dgkMK0O
NDYAn06+/cyLX0CiQJLSg+6IuKS8tCsx
=kcom
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
|