I was not replying to any post by you. I was replying to a post by a fellow
named Dan.
He states "I have been successful using the charset filters on HTTP posts
and XML"
I am not sure I can respond to your comments since it seems that we talk
about different topics. In either case, why vent?
E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 12/2/2009 5:34 AM, André Warnier wrote:
> Just a quick line : Thank you for the test, and I am not forgetting
> this, since I would really like to get to the bottom of it.
> I am fairly busy for the next 2 days however, and will revisit that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Elli,
On 12/2/2009 2:40 AM, Elli Albek wrote:
> On your Linux box type “locale” + enter. The results should be UTF 8. If not
> change it.
I can have my locale set to whatever I'd like, thank you very much.
> You can also set it in the file encoding
Hi.
Just a quick line : Thank you for the test, and I am not forgetting
this, since I would really like to get to the bottom of it.
I am fairly busy for the next 2 days however, and will revisit that
after the current rush.
I have a definite case where I am forced to set Tomcat's startup locale
Hi,
On your Linux box type “locale” + enter. The results should be UTF 8. If not
change it. You can also set it in the file encoding java environment
variable as suggested above as extra safety measure.
Tomcat’s logic of determining the encoding from the request only applies
when Tomcat is parsin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 11/30/2009 7:39 PM, André Warnier wrote:
> Well, just make a simple test :
> (I don't really know how to handle JSP pages, I only do servlets and
> filters, otherwise I'd do it myself).
:)
> - create a simple html form with a UTF-8 charse
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
That applies also to webapps which read posted input, unless you are
careful.
No! The default encoding for servlets is ISO-8859-1 unless the client
specifies the encoding (which many do not). The value for file.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 11/27/2009 11:05 AM, André Warnier wrote:
> A bit more detail : in java, if you open a text input stream without
> specifying in which encoding it is, it will default to the "platform"
> encoding, which in this case is the locale setting of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Juha,
On 11/28/2009 12:31 PM, Juha Laiho wrote:
> Dan Bagley wrote:
>> In the failing environment I have the following env settings
>>
>> LANG=en_GB.UTF-8
>>
>> the successful env is set to
>>
>> LANG=en_UK
>
> I'm pretty certain that is the reason f
Dan Bagley wrote:
In the failing environment I have the following env settings
LANG=en_GB.UTF-8
the successful env is set to
LANG=en_UK
I'm pretty certain that is the reason for the differences you're seeing.
Try starting the Tomcat in the failing environment with LANG set equal
to that in y
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 insta
We are using spring so I may switch to this, but we are currently using
the charset filters as specified in the Tomcat samples and they seem to
work ok for XML so not sure whether changing the charsetFilter will
help with the plain text stream problem.
cheers anyway
Pid wrote:
On 27/11/2009
On 27/11/2009 16:12, Gatos wrote:
It might solve your problems:
charsetFilter
org.springframework.web.filter.CharacterEncodingFilter
encoding
ISO-8859-1
charsetFilter
/*
... it might, but only if you're using Spring.
p
On Fri, Nov 27, 2009 at 6:05 PM, André
It might solve your problems:
charsetFilter
org.springframework.web.filter.CharacterEncodingFilter
encoding
ISO-8859-1
charsetFilter
/*
On Fri, Nov 27, 2009 at 6:05 PM, André Warnier wrote:
> Continuing to top-post thus :
>
> If you have some systems working and others not,
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 instance and it works and then
post the same file into a tomcat 5.5 instance on Linux and it doesn't
work. But then I post again onto Tomcat 6 insta
Continuing to top-post thus :
If you have some systems working and others not, check if all Tomcat's
(or rather, their JVMs) start under the same "locale" setting.
This is not a "good" reason, but it is often a reason for such things.
A bit more detail : in java, if you open a text input strea
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 identical and s
Dan Bagley wrote:
The file is identical and static, I post the same file from my windows
desktop into a locally running tomcat instance and it works and then
post the same file into a tomcat 5.5 instance on Linux and it doesn't
work. But then I post again onto Tomcat 6 instance on Linux and it
On 27/11/2009 12:30, Dan Bagley wrote:
The file is identical and static, I post the same file from my windows
desktop into a locally running tomcat instance and it works and then
post the same file into a tomcat 5.5 instance on Linux and it doesn't
work. But then I post again onto Tomcat 6 instan
The file is identical and static, I post the same file from my windows
desktop into a locally running tomcat instance and it works and then
post the same file into a tomcat 5.5 instance on Linux and it doesn't
work. But then I post again onto Tomcat 6 instance on Linux and it works.
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 issue.
Let's eliminate
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 issue.
Pid wrote:
On 27/11/2009 11:16, Peter Crowther
On 27/11/2009 11:16, Peter 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 th
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 issues aren't a problem for the
Hi Peter,
Thanks for the heads up, the server build we are having problem with is
Server version: Apache Tomcat/5.5.20
Server built: May 8 2007 10:23:38
Server number: 5.5.20.0
OS Name:Linux
OS Version: 2.6.9-78.0.13.ELsmp
Architecture: amd64
JVM Version:1.5.0_16-b02
JVM Ven
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 text, on windows it works and
> Linux using Tomcat 6.0 it works.
Dan, exact
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
27 matches
Mail list logo
