it to the list as informations
that some library outside of tomcat can munge UTF-8 encoding.
-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 4:10 PM
To: Tomcat Users List
Subject: Re: UTF-8 encoding problems
Thompson,Roger wrote:
I saw that--All
Thompson,Roger wrote:
So there is something in log4j that munges the parameter sstring.
Unlikely. Chances are there is something in Tomcat's internal debug logging
that does this. It isn't entirely surprising. The request dumper valve has
a similar side-effect.
that some library outside of
Environment:
Tomcat 5.5.20, no apache frontend.
Running XSLTFIlter and urlrewrite in front of the tomcat.
WE are implementing a RESTful webservice (tspilot) on top of a SRU service
on the connector going into tomcat I have:
Connector port=1
allowTrace=true
Thompson,Roger wrote:
WHere else besides the connector definition in the server.xml, should I look to
find this. The implementor of the SRW/U code is convinced that the problem is
in tomcat some where as he does not get this same error.
http://wiki.apache.org/tomcat/FAQ/CharacterEncoding#Q4
Thompson,Roger wrote:
I saw that--All it really says is to set URIEncoding=UTF-8 the tips
say to use POST-- cannot do in a RESTful service.
Have you actually tried the test? Did it work? If you read the sample code
it also points to a number of other things the service needs to do in terms
thanks, will try the TcpMon
-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 4:10 PM
To: Tomcat Users List
Subject: Re: UTF-8 encoding problems
Thompson,Roger wrote:
I saw that--All it really says is to set URIEncoding=UTF-8 the tips
say
