[TAPESTRY-2501] Form input not correctly decoded in case of non-english charsets

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.13
• Fix Version/s: 5.0.14
• Assignee: Howard Lewis Ship
• Reporter: Vjeran Marcinko
• Created: 03/Jul/08 05:15
• Updated: 29/Jul/08 20:22
• Resolved: 29/Jul/08 20:22

Description

This problem occurs because major browsers don't conform to standards which says that client charset should be sent via "content-type" HTTP header to server.
Everything is well described in this article:
http://www.crazysquirrel.com/computing/general/form-encoding.jspx

I guess this is closely related to submitted issue:
https://issues.apache.org/jira/browse/TAPESTRY-915

So, fix should be that
HttpServletRequest.setEncodingCharset("UTF-8"); (I guess charset should be configurable somehow)
is set in tapestry filter prior to anyone fetching any parameter value.

Issue Links

• is part of: TAPESTRY-2543 Simplify Tapestry to use UTF-8 (or another, configurable character set) across the entire application