Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Message-ID: <4AC4867E.9070106@ice-sa.com>
Date: Thu, 01 Oct 2009 12:37:50 +0200
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: Tomcat Users List <users@tomcat.apache.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Default character encoding for ServletRequest
References: <4AC479F3.8090005@switch.ch>
In-Reply-To: <4AC479F3.8090005@switch.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Halm Reusser wrote:
> Hi,
> 
> Calling <%= request.getCharacterEncoding() %> in a jsp deployed in a 
> Tomcat 6.0.20 container returns null.
> 
> Is there any possibility to force a default CharacterEncoding for such 
> requests?
> 
Don't worry, there is already a default.
The only problem is to figure out what it is..
;-)

My guess, at this stage, is that it is either iso-8859-1 (which is the 
default charset for the HTTP protocol), or else it is tied to whatever 
"locale" your Tomcat's JVM has been started under.
It would also depend on whether the request which you are processing is 
a GET or a POST.
And, whatever you would decide to set as a default at the server level, 
you can still not be quite sure that the client's choice matches yours.

Confused enough ?
Sorry, but that's about the most definite thing that can be said on the 
subject, considering the various often conflicting specifications that 
play a role here.

If the past is any guide however, this post will probably trigger a 
lively discussion.

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