tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Tomcat bad char issue with new cluster
Date Wed, 07 Oct 2015 15:52:46 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Saurav,

On 10/6/15 9:37 AM, Saurav Maulick wrote:
> Please find my answer below
> 
> 
> *Two new clusters or two new nodes added to an existing cluster?*
> 
> Two Nodes
> 
> 
> *What is the difference between the conf/server.xml on a "working"
> server and one of these new servers that is misbehaving?*
> 
> No difference. Apart from Server port –Configuration, non-SSL 
> HTTP/1.1Connector port Configuration, AJP 1.3 Connector port
> Configuration, and jvmRoute Configuration
> 
> 
> *Identical WAR files deployed to all servers?*
> 
> Yes all the nodes have identical WAR file

The problem here is usually with the <Connector> URIEncoding setting
(probably should be UTF-8 these days) or with clients who send a
content-type header without specifying the character encoding, leaving
the server to default to ISO-8851-1 (instead of UTF-8, which ought to
be the default these days).

Tomcat 8 uses UTF-8 as the default <Connector> URIEncoding, unless the
system property org.apache.catalina.STRICT_SERVLET_COMPLIANCE is set
to true. Tomcat 5.5 *always* uses ISO-8859-1 as the default.
http://tomcat.apache.org/tomcat-8.0-doc/config/http.html
http://tomcat.apache.org/tomcat-5.5-doc/config/http.html

Mikel was asking about <filter> in Tomcat's conf/web.xml because it's
typical these days to use a SetCharacterEncodingFilter to override the
HTTP-spec-defined requirement that ISO-8859-1 be used when the client
does not specify a character set.
http://tomcat.apache.org/tomcat-8.0-doc/config/filter.html#Set_Character
_Encoding_Filter
http://tomcat.apache.org/tomcat-5.5-doc/config/filter.html#Set_Character
_Encoding_Filter

Finally, you should double-check your database connection
configuration. If you have the character set incorrect, there, you can
break data in both directions from the database.

Can you tell if the characters are broken for GET vs POST requests?
Can you check to see if this is an input or output problem? You can
check the string in the database to see if the error is present there?

Have a read through this document; it will help you look at all the
places where there might be a problems:
http://wiki.apache.org/tomcat/FAQ/CharacterEncoding#Q8

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJWFT/OAAoJEBzwKT+lPKRYgKgP/iIkQe7b4K4NLPCUENIQY+xU
8brkeF1z60kJdtoBQvx0FtzpO6ri0GUXKK9S/3PNxPq8YlMm+lLc3lMhjHD8PlVR
jx7zlvBTdpfyYm2flB3WHWP5W36Ii1kkUlCdVv1uaemov9++AA/ACK1HDUAWUD+J
Jiho+tg+9qjoOAVcUVGXkLb1pkeXB8GZb5pbdG9w6igKevcAOxYs0yoBJ1FLx08A
0ONpGI4VJplvFI1UyOBwU8hqAuUb5d4PUxmwPCoE4j7vcadsgJSxOikClPHQQYfN
GrQtSgo0MzMfAKDB4AHZtWkX/P6Yj79977y9W8fcDc27NtOoJeZzEMTsQfG/kzeK
UyJxu+F9C2l0iTGx+e/BZjYf0fvfBk6wxzivPCb6UWZhjHxNkrFW8GNZio5G67iK
jZ+qNbk6QNiEbFdCZVgUrTAF2H6LL0mW7hwhLdB4+ASeD3xwTsXVg+IuR7DPxjOp
bNIOin6IKgIDKpQYPsZKw8y20XomxDhV7FxTbmLc//ApXultUiZ5DhNBB+kD63+b
pXkL6RT7GUohVN2lF7J02A8LlyQgGRqOakTjJ3swAfVGlcT+eleleBUUGvk+EaQQ
QJPlIi7dO+Rn7El7o/BNByaBZZ3SfJn8BOhwHaKQWZJjSBxpXGinv3SyFxKjh59c
V3Ufu0KAnJ9I1NRqv/4D
=owkM
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message