You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/06/26 16:11:45 UTC
[jira] Updated: (SLING-559) Request parameter re-encoding does not
work
[ https://issues.apache.org/jira/browse/SLING-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-559:
------------------------------------
Attachment: SLING-559-GET.esp
Simple test script used to test the fix for this issue. To use this script store it at /apps/sling/nonexisting/GET.esp and access /missing.html on the Sling server.
> 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
> 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.