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 (nike.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.218.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=f9eqP4cdxDk02DEQea3ZEuWUIkiIfa5HNqc1be1gZLzJbh0jwcYZeXgPlWwLD2nLSE
         CqL0inbigUnL6P1SEgjfsmRQalu9ihLYFqBFx4x7pZnwtfh+p0mirgMzXyJ1M3x/0h2b
         psKJRBW2R5vwzvYyVPJCptAcQO6cHBe6ZErQE=
MIME-Version: 1.0
In-Reply-To: <4A317C98.50408@apache.org>
References: <20090610233458.049422388882@eris.apache.org>
	 <4A312988.2040000@apache.org>
	 <427155180906111041j32807c5ap7868bfd210902e27@mail.gmail.com>
	 <4A315DD0.8070706@apache.org>
	 <427155180906111432h449f2deg7505055d6d202f2@mail.gmail.com>
	 <4A317C98.50408@apache.org>
Date: Fri, 12 Jun 2009 20:55:32 +0400
Message-ID: <427155180906120955l72386104m28054427a2b597a0@mail.gmail.com>
Subject: Re: svn commit: r783570 - /tomcat/current/tc4.1.x/STATUS.txt
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2009/6/12 Mark Thomas <markt@apache.org>:
> Konstantin Kolinko wrote:
>> Thank you for detailed explanation.
>>
>> My analysis is the following:
>> hres.setLocale(locale);
>> call -> =A0o.a.c.Response.setLocale() -> o.a.c.connector.ResponseBase.se=
tLocale()
>>
>> In o.a.c.connector.ResponseBase.setLocale() it calls
>> CharsetMapper.getCharset(locale)
>> and updates the contentType header.
>>
>> The problem is with those locales for which CharsetMapper.getCharset(loc=
ale)
>> returns null. =A0There is an error in ResponseBase.setLocale() that it w=
ill set
>> =A0contentType =3D contentType + ";charset=3Dnull"
>> in those cases. How about fixing that?
>>
>> My understanding is that it will solve the issue, and won't change the
>> error page encoding for existing applications.
>>
>> We cannot fix CharsetMapper, because it can be overwritten, but we can
>> fix those places where it is called.
>>
>> Here is the patch:
>> http://people.apache.org/~kkolinko/patches/2009-06-12_tc41_CharsetMapper=
.patch
>
> Yep, that would also fix the issue. However, that patch changes the
> behaviour of setLocale(). Whilst it shouldn't cause a regression there
> is a risk that it might for some applications.
>
> The 'right' / 'proper' fix for TC4 would be to implement
> STRICT_SERVLET_COMPLIANCE and in particular, the change to getWriter().
> Again, there is the risk of regression with this approach.
>
> TC6 and TC5 already use UTF-8 for Tomcat's default error page. The
> proposed TC4 page brings TC4 into line with TC5 and TC6.
>
> My personal preference is for the small as possible 'band-aid' approach
> to minimise the regression risk.
>

I do not like that your patch changes behavior where it was not
broken previously.

Theoretically, there might be someone who relies on the encoding
of those error pages, but, well, those pages are for humans,
and we are free to change them for readability or for any other purpose.

OK, I give my +1.


Anyway, just as a thought,
here is another version of setLocale patch,
http://people.apache.org/~kkolinko/patches/2009-06-12_tc41_CharsetMapper_v2=
.patch

I am not very interested in it, though.

Best regards,
Konstantin Kolinko

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