> Oh! This sounds, like it's a "bug" and like it might be fixed in tomcat
> 6, for example. Now i'm curious, and will test tomcat 6 ...
Ahh damn - i didn't read properly.
It's the old story: it's NOT a bug, it's a feature ;-)
signature.asc
Description: OpenPGP digital signature
>> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Sven Köhler
>> Subject: charset for querystring decoding
>>
>> And if you know: what's the reason, that the charset is not
>> configurable via request.setCharacterEncoding() ?
>
> Might want to che
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Sven Köhler
> Subject: charset for querystring decoding
>
> And if you know: what's the reason, that the charset is not
> configurable via request.setCharacterEncoding() ?
Might want to check out the FAQ entr
Hi,
as far as i remember, tomcat always uses a default-charset for decoding
the querystring. A call to request.setCharacterEncoding() only matters
for decoding POST-data.
Somewhere, this charset can be changed - for example to UTF-8.
Where can it be changed?
And if you know: what's the reason, t
