[
https://issues.apache.org/jira/browse/TOMEE-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801662#comment-13801662
]
Kristof Neirynck commented on TOMEE-1063:
-----------------------------------------
[[email protected]]: Adding a filter with setCharacterencoding seems to be
unnecessary.
[~romain.manni-bucau]: Yes and this is indeed necessary.
Adding the Content-Type with ServletFilter was the missing piece of the puzzle.
> URL encoding problems when using ?faces-redirect=true&includeViewParams=true
> ----------------------------------------------------------------------------
>
> Key: TOMEE-1063
> URL: https://issues.apache.org/jira/browse/TOMEE-1063
> Project: TomEE
> Issue Type: Bug
> Affects Versions: 1.5.2, 1.5.3, 1.6.0
> Reporter: Kristof Neirynck
>
> This is basicly the same bug as
> https://java.net/jira/browse/JAVASERVERFACES-2440
> I've created a simple testproject for it here:
> https://github.com/Crydust/facesredirect
> 1. submit a field with an umlaut or other unicode character
> 2. return to the view with ?faces-redirect=true&includeViewParams=true
> 3. the url contains a wrongly encoded string
> 4. the value of the viewParam is also wrongly encoded now
> This can be reproduced on TomEE 1.5.2, 1.5.3-SNAPSHOT, 1.6.0-SNAPSHOT and
> even Glassfish 3.1.2.2.
> This seems to work correctly on JBoss eap 6.1 and Glassfish 4.0.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
