I found this:
When processing a servlet request, the server uses the following order
of precedence, first to last, to determine the request character
encoding:
* The getCharacterEncoding() method
* A hidden field in the form, specified by the
form-hint-field attribute of the parameter-encoding element in the
sun-web.xml file
* The default-charset attribute of the parameter-encoding
element in the sun-web.xml file
* The default, which is ISO-8859-1
so, what is the recommended way to make a portable and robust code here ?
to create a filter just to force an encoding ?? to move to latin1 and
to believe the rest of the world will always be latin1 ? :)
2009/3/17 Felipe Gaúcho <fgaucho_at_gmail.com>:
> I have this registration module, that sends to the user an email with
> a link to click.. once the user clicks this link, the account is
> activated..
>
> it works, but I have an encoding problem caused by Glassfish misconfiguration..
>
> if I get the encrypted+base64+urlencoded string and apply to my
> cleaner method, it works perfectly..
>
> but if I get the same url and submit to my method through a glassfish
> hosted url, it fails..
>
> so, Glassfish web app server is transforming the string somehow..
>
>
> the test string:
>
> DSS8Sh5njPYm5JoF1OuE%2F%2F9eK0pqPlfV0mOSy7BRSD4ESO1gO%2Bs%2FTQ%3D%3D
>
> where I can configure Glassfish to accept requests with UTF-8
> parameters ?? or which encoding should I use ??
>
>
> --
>
> Please help to test this application:
> http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces
>
--
Please help to test this application:
http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces