[
https://issues.apache.org/jira/browse/TAPESTRY-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617622#action_12617622
]
Howard M. Lewis Ship commented on TAPESTRY-2501:
------------------------------------------------
Looking at the code, I think I see how TAPESTRY-1605 is not quite fixed. The
check for query parameters occur before there's a chance to set the request
encoding.
> 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
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
