[
https://issues.apache.org/jira/browse/WICKET-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-3578.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC4
Improved with r1096795.
> 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
> Assignee: Martin Grigorov
> Fix For: 1.5-RC4
>
> 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
