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 2007/11/29 01:28:43 UTC
[jira] Closed: (TAPESTRY-1723) tapestry-upload does not use
character encoding
[ https://issues.apache.org/jira/browse/TAPESTRY-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1723.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.7
Assignee: Howard M. Lewis Ship (was: Daniel Gredler)
> tapestry-upload does not use character encoding
> -----------------------------------------------
>
> Key: TAPESTRY-1723
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1723
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-upload
> Affects Versions: 5.0.5
> Reporter: Christian Köberl
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.7
>
> Attachments: fileupload_encoding_20070827.patch
>
>
> tapestry-upload ignores the character encoding set in the request and falls back to default character encoding.
> The problem is that when extracting the parameter values the FileItem#getString() instead of FileItem#getString(String encoding) is used. The same problem is described and solved in JBoss Portal CMS:
> See also: http://jira.jboss.com/jira/browse/JBPORTAL-1550
> The getString method should be called with the encoding of the request:
> item.getString(request.getCharacterEncoding());
--
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