[
https://issues.apache.org/jira/browse/SLING-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-559.
-------------------------------------
Resolution: Fixed
Fix Version/s: Engine 2.0.4
In Rev. 671908 I committed the fix described in my previous comment. I tested
this fix with the Sling standalone application which uses an embedded Jetty
Servlet Container as well as with Day's own Servlet Container.
Please close this issue if it fixes your issue. Thanks.
> Request parameter re-encoding does not work
> -------------------------------------------
>
> Key: SLING-559
> URL: https://issues.apache.org/jira/browse/SLING-559
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.0.2
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
> Fix For: Engine 2.0.4
>
> Attachments: SLING-559-GET.esp
>
>
> Issue SLING-508 introduced a smart way to re-encode request parameters, if
> they are sent in a different encoding that the default.
> imo there is a bug that causes this functionality to fail:
> in ParameterSupport.getContainerParameters(....) new
> ContainerRequestParameter are generated with the respective encoding. but the
> constructor does never call setEncoding() and the re-encode is never
> performed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
