[jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-2479) Character encoding incorrect with CASAuthenticationValve enabled
Martin Putz (JIRA)
jira-events at lists.jboss.org
Fri Jul 2 10:31:46 EDT 2010
[ https://jira.jboss.org/browse/JBPORTAL-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Putz resolved JBPORTAL-2479.
-----------------------------------
Fix Version/s: Identity-1.1
Resolution: Done
Committed rev 13954 on JBP_IDENTITY_BRANCH_1_1, next identity tag containing this fix will be 1.1.3.
Set the file.encoding property as a VM argument to override the default encoding.
> Character encoding incorrect with CASAuthenticationValve enabled
> ----------------------------------------------------------------
>
> Key: JBPORTAL-2479
> URL: https://jira.jboss.org/browse/JBPORTAL-2479
> Project: JBoss Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Portal Identity
> Affects Versions: Identity-1.1, 2.7.2 Final
> Reporter: Martin Putz
> Assignee: Martin Putz
> Fix For: Identity-1.1
>
> Attachments: JBPORTAL-2479.patch
>
>
> With CASAuthenticationValve enabled, data inserted is returned garbled. In the invoke() method, the parameters are retrieved from the request object. This parses the parameters before any character encoding has been set, but it sets the parameters parsed flag to true. Therefore the encoding will never get set.
> To get around this, request.setCharacterEncoding(..) needs to be called before any request parameters are retrieved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list