Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of andrejohn.mas@gmail.com
 designates 209.85.162.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=tjJlESRnHeDStjGLpqhRGW9rq7HGV6WPdbqFj1fXh1ypQy0uiV05mYRNDCDOodnRR8
         8jyIyVHlYkg3pjeuHvS7B+l+LmshXSRXXZ7tQUPxKM/p36/ggoOINUkR7NmUiGOSJ+V8
         jsY3AQ/rkmlEH64za+TJVctuBKTicfuHRZTPY=
Message-Id: <0DDB2311-4BF5-473A-B399-1AAD8AD36BD7@gmail.com>
From: Andre-John Mas <andrejohn.mas@gmail.com>
To: "Tomcat Developers List" <dev@tomcat.apache.org>
In-Reply-To: <48EA9B3F.4090507@joedog.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: UTF-8 POST request results in corrupted data
Date: Mon, 6 Oct 2008 20:58:17 -0400
References: <67ca80b70810061233x476bdef9y34ffbf041b6c7878@mail.gmail.com>
 <48EA9B3F.4090507@joedog.org>

Just to repeat what I stated in the ticket:

The problem I have with the suggested approach is that it treats UTF-8 =20=

as an
exception, rather that a norm for my whole application server. I am =20
not sure
that I should be having to be specifying the encoding before handling =20=

every
request. For a web site that is completely in UTF-8 that is a lot of =20
duplicated
code.

Also, I ask the question why should we allow one behaviour for the URI =20=

in the
container and not allow for the same with regards to the POST?

Andr=E9

On 6-Oct-08, at 19:11 , Tim Funk wrote:

> Before reading the POST body - you should first be doing this:
> request.setCharacterEncoding("UTF-8")
>
>
> -Tim
>
> Andr=E9-John Mas wrote:
>> Hi,
>> I have opened issue 45957, for an issue that has bothered me for a =20=

>> while:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=3D45957
>> To resume:
>> Currently in Tomcat 5 if a request is received containing UTF-8
>> content then any accents or non-Roman characters are corrupted, since
>> there is an assumption
>> the POST request is ISO-8895-1 (latin1). For example '=E9' becomes =20=

>> '=C3(c)'
>> Has anyone looked into this as part of a separate task, otherwise I
>> would be willing to see what could be done.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>


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