You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/07/29 22:23:31 UTC
[jira] Closed: (TAPESTRY-2501) Form input not correctly decoded in
case of non-english charsets
[ https://issues.apache.org/jira/browse/TAPESTRY-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2501.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.14
Assignee: Howard M. Lewis Ship
TAPESTR-2543 now ensures that all incoming requests have their request encoding properly set as query parameters are extracted.
> Form input not correctly decoded in case of non-english charsets
> ----------------------------------------------------------------
>
> Key: TAPESTRY-2501
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2501
> Project: Tapestry
> Issue Type: Bug
> Affects Versions: 5.0.13
> Reporter: Vjeran Marcinko
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.14
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org