Return-Path: 
 <users-return-205341-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 84553 invoked from network); 27 Nov 2009 16:16:56 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 27 Nov 2009 16:16:56 -0000
Received: (qmail 36615 invoked by uid 500); 27 Nov 2009 16:16:52 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 36557 invoked by uid 500); 27 Nov 2009 16:16:52 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 36546 invoked by uid 99); 27 Nov 2009 16:16:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Nov 2009 16:16:51 +0000
X-ASF-Spam-Status: No, hits=0.7 required=10.0
	tests=SPF_SOFTFAIL
X-Spam-Check-By: apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 pid@pidster.com does not designate 209.85.219.223 as permitted sender)
Received: from [209.85.219.223] (HELO mail-ew0-f223.google.com)
 (209.85.219.223)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Nov 2009 16:16:41 +0000
Received: by ewy23 with SMTP id 23so1892163ewy.24
        for <users@tomcat.apache.org>; Fri, 27 Nov 2009 08:16:21 -0800 (PST)
Received: by 10.213.24.1 with SMTP id t1mr1042078ebb.57.1259338581296;
        Fri, 27 Nov 2009 08:16:21 -0800 (PST)
Received: from phoenix.config (94-193-98-41.zone7.bethere.co.uk
 [94.193.98.41])
        by mx.google.com with ESMTPS id 14sm992673ewy.15.2009.11.27.08.16.18
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Fri, 27 Nov 2009 08:16:20 -0800 (PST)
Message-ID: <4B0FFB4F.3040100@pidster.com>
Date: Fri, 27 Nov 2009 16:16:15 +0000
From: Pid <pid@pidster.com>
Reply-To: pid@pidster.com
Organization: Pidster Inc
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB;
 rv:1.9.1.5) Gecko/20091121 Thunderbird/3.0
MIME-Version: 1.0
To: users@tomcat.apache.org
Subject: Re: Char Encoding text streams on Tomcat 5.5 and Linux
References: <4B0FAA19.7090701@metadatatechnology.com>
	 <e0c148a0911270258u74aa4da9s29eb4c44078a8899@mail.gmail.com>
	 <4B0FB287.5060007@metadatatechnology.com>	 <4B0FF8E4.4060205@ice-sa.com>
 <c0364faa0911270812p62af378v4419ec826548c440@mail.gmail.com>
In-Reply-To: <c0364faa0911270812p62af378v4419ec826548c440@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org

On 27/11/2009 16:12, Gatos wrote:
> It might solve your problems:
>
>   <filter>
>   <filter-name>charsetFilter</filter-name>
>   <filter-class>org.springframework.web.filter.CharacterEncodingFilter</filter-class>
>   <init-param>
>   <param-name>encoding</param-name>
>   <param-value>ISO-8859-1</param-value>
>   </init-param>
>   </filter>
>
>   <filter-mapping>
>   <filter-name>charsetFilter</filter-name>
>   <url-pattern>/*</url-pattern>
>   </filter-mapping>

... it might, but only if you're using Spring.


p


> On Fri, Nov 27, 2009 at 6:05 PM, André Warnier<aw@ice-sa.com>  wrote:
>
>> 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 stream without
>> specifying in which encoding it is, it will default to the "platform"
>> encoding, which in this case is the locale setting of the process which runs
>> the Java JVM which runs tomcat.
>> That applies also to webapps which read posted input, unless 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 Bagley wrote:
>>
>>> 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 Vendor:     Sun Microsystems Inc.
>>>
>>>
>>> And yep this is a customer support issue as the later versions of Tomcat
>>> have not been approved through there security review process, so they're
>>> unable to move onto the later versions.
>>>
>>> I'll double check Tomcat 5.5.28, but there still may be issues with the
>>> client moving onto this release.
>>>
>>> Cheers
>>>
>>> Dan
>>>
>>>
>>>
>>> Peter Crowther wrote:
>>>
>>>> 2009/11/27 Dan Bagley<dan.bagley@metadatatechnology.com>:
>>>>
>>>>
>>>>> 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, exactly which version(s) of 5.5 and 6.0 are you using?  Also,
>>>> which JVM are you using on each of these platforms?
>>>>
>>>> I'm not sure I have a solution for the problem, but you're more likely
>>>> to get useful answers off the list if we have some reasonably precise
>>>> version information ;-).  If you're not testing on the latest 5.5.x
>>>> (which is 5.5.28), I've no doubt you'll also get a "does it still fail
>>>> on the latest 5.5?" question.
>>>>
>>>>  From your question, I'm assuming you have a need to support older
>>>> Tomcat versions rather than just say "first install Tomcat 6.0.x".  Is
>>>> that due to customers having older versions installed, or QA issues,
>>>> or some other reasons?
>>>>
>>>> - Peter
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>


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