[
https://issues.apache.org/jira/browse/WICKET-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014760#comment-13014760
]
Attila Király commented on WICKET-3578:
---------------------------------------
An alternative solution could be to implement this in the WicketFilter
directly: it could be off by default and turned on with a filter init-param in
web.xml.
Btw. I found an interesting info in the javadoc of
o.a.w.settings.IRequestCycleSettings.getResponseRequestEncoding():
"wicket now uses multipart/form-data for it's forms"
This explains why this was not a problem in the past: multipart requests are
parsed by wicket (with the correct encoding) and not by the container. However
wicket is not using "multipart/form-data" for every form now: neither in 1.4
nor in 1.5.
> Wicket should set the character encoding on requests
> ----------------------------------------------------
>
> Key: WICKET-3578
> URL: https://issues.apache.org/jira/browse/WICKET-3578
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Reporter: Attila Király
> Attachments: fix-WICKET-3578.patch, wicket-3578.zip
>
>
> Browsers should but actually do not send encoding information with requests.
> Because of this servlet containers (like Tomcat) use the default "ISO-8859-1"
> encoding to decode POST parameters in non-multipart requests. This is wrong
> in case the webapp is using a different encoding (like UTF-8).
> To workaround this it is possible to specify the correct encoding on the
> server side trough javax.servlet.ServletRequest.setCharacterEncoding(String).
> This can be done in a filter (I use spring's CharacterEncodingFilter for
> this, but Tomcat also has SetCharacterEncodingFilter for the same). It would
> be nice if wicket could do this out of box so no additional filter would be
> needed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
