In the failing environment I have the following env settings
LANG=en_GB.UTF-8
the successful env is set to
LANG=en_UK
André Warnier wrote:
Juha Laiho wrote:
Dan Bagley wrote:
The file is identical and static, I post the same file from my
windows desktop into a locally running tomcat
s you are
careful.
You will not see this issue with XML input, because XML contains
either an
explicit charset declaration, or defaults to UTF-8. So the XML parse
always
knows. But pure text is another matter.
There is a lot more to say about these matters, but this will get you
started.
Dan B
Tomcat 6 is on a different server, so it could be an environment issue,
rather than a release issue.
I'm just setting up Tomcat 5.5 on the Tomcat 6 server so I can rule that
out.
Homing in on the bug, I hope.
Pid wrote:
On 27/11/2009 12:30, Dan Bagley wrote:
The file is identica
Pid wrote:
On 27/11/2009 12:16, Dan Bagley wrote:
Indeed that would be ironic, :-)
I've just checked version 5.5.28, and unfortunately we have the have the
same problem.
I'm just checking the JVM as this version on the working machine is
using Java 6 (1.6.0-b09) , that could be an
r Crowther wrote:
2009/11/27 Dan Bagley:
Server version: Apache Tomcat/5.5.20
That's 2.5 years old and has a number of known security
vulnerabilities. Given that the issue is the client's security review
process, have they reviewed later 5.5.x releases and verified that the
known iss
s with the
client moving onto this release.
Cheers
Dan
Peter Crowther wrote:
2009/11/27 Dan Bagley :
now when processing the plain text stream the accented characters are being
corrupted even though the stream is being set to UTF-8. This is only
happening on Linux and Tomcat 5.5 with plain
Hi,
I'm having real problem with character encoding, I have been successful
using the charset filters on HTTP posts and XML streams without any
problems. But recently we've extended the interface to accept plain
text, now when processing the plain text stream the accented characters
are bei
