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:56:57 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Saurav,

On 10/7/15 11:52 AM, Christopher Schultz wrote:
> 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_Charact
er
>
> 
_Encoding_Filter
> http://tomcat.apache.org/tomcat-5.5-doc/config/filter.html#Set_Charact
er
>
> 
_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

Also:
http://wiki.apache.org/tomcat/FAQ/CharacterEncoding#Q5

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

iQIcBAEBCAAGBQJWFUDJAAoJEBzwKT+lPKRYlQMQAJxJaHq2X448+O0YBbzOhR+r
1eUTGgZzKpPmU+yvqXXuztxPf0fzQlck/juETnEaF+vnqncmcPmiFb8D+wLTwg0x
Zw62mRfy5rh4jRMHstU1QheeY2c0Bv0iewhqqdMP19uAgwStn95Oov9EBMKYmka2
2jkmw2jfyVzVYoosJo1AqQ04f0UNv2DOSYnQrh/XudpCHK2SGcXy8efn3upMO28q
5OJOlLCEMSPGyQv2W97AwfcG5cAZq+VJglyVGmz/rU3JrO1b3Gqc+sqtcjsJ0/kq
MlMn6WS9QNCgKbm/sMjsLD/wNZpWhx1IbyateT175JGS4z+VFOSDBfLNL9eUc+eC
k61b+slemyt3aRYysryKlP7GEgl+Kja9v9FxCzkxOrRs8RY8ymKe0HcFRvLarVwt
kYDE7ByKpAsyAPEBRYXE4TXuesc/KlC2eCHWBIFE/2/bznGf8vHjwCjcJSz3j8I9
nm6b4IAUSOHrXECBBdQ5Yzx3pKdCUo0I7TTF7JzkZ1md06JjJOMvUL5b2wFzIFIM
Tv3Nk2NI4iiHzU1nqr1QAoBdHVpC25/QfgoCtSSJPVA4/Y3rZ2oBQQPvr0DiDDR6
uc7zwApqiFXtP2onLkCSJJxL3YTkHoTrmRzSVgbGNw0pk6NhadxBqH5DV/Sn6PPX
y+M6jqRkfQ7lvH3bMxqq
=gsYD
-----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