tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <...@tapestry.apache.org>
Subject [jira] Commented: (TAPESTRY-2501) Form input not correctly decoded in case of non-english charsets
Date Tue, 29 Jul 2008 00:10:33 GMT

    [ https://issues.apache.org/jira/browse/TAPESTRY-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617623#action_12617623

Howard M. Lewis Ship commented on TAPESTRY-2501:

That check occur when trying to restore persistent fields, potentially from stored request
state (the t:state:client query parameter).

> 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
> 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

View raw message