J. Patterson Waltz III wrote:
Merci Guillaume,
I had actually seen the references to the Filter solution in the comments of
Struts bug 16191 in Bugzilla:
http://issues.apache.org/bugzilla/show_bug.cgi?id=16191
I will try that out and see if it improves my results.
I remain perplexed at what changes between versions 1.1 and 1.2.4 of Struts
caused it to become susceptible to this problem. Any ideas on that?
Patterson
P.S. - I know how to view the headers of replies sent from the server to the
browser, but am not sure how to get at those sent from the browser to the
server, to make sure that they are indeed UTF-8. Any suggestions?
in article [EMAIL PROTECTED], Guillaume Cottenceau at [EMAIL PROTECTED]
wrote on 4/01/05 16:40:
Most probably the browser is sending data in UTF-8 but doesn't
say so with charset= in the Content-Type header. If you're
confident enough that the browsers will send UTF-8 (which should
be the case if they are encoded in UTF-8 and you use
accept-charset in the forms), you can use a filter which forces
the HTTP request to be seen as UTF-8 in input (for example
filters/SetCharacterEncodingFilter which is bundled with
tomcat)[1].
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
One way woulb be to set up a proxy that your browser uses to connect to
the web. I used to use web scarab.
http://www.owasp.org/software/webscarab.html
-josh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
