Thanks, I will try CharacterEncodingFilter!
I will lookup in the code were filtering takes place, because the
problem is rather that it looks like the form data are filtered twice.
In addition, do I remember right that there used to be a cocoon servlet
setting,
<init-param>
<param-name>form-encoding</param-name>
<param-value>UTF-8</param-value>
</init-param>
Cheers, thanks for the hint. I will post the result... I will certainly
not be the only person who is confronted with this problem.
Jos
On Mon, 2010-01-11 at 08:54 +0000, Dominic Mitchell wrote:
> 2010/1/10 Jos Snellings <[email protected]>
> This is not a specific cocoon issue, I believe. It probably
> has to do
> with Tomcat 5.5.27.
> request.setCharacterEncoding simply does not work; it does not
> change a
> thing.
> request.getCharacterEncoding returns nothing.
>
> You have to call request.setCharacterEncoding() really early for it to
> have any impact. Your best bet is to look at spring's
> CharacterEncodingFilter. You can add that to your web.xml to get the
> character set defined very early on.
>
> -Dom
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
