You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2015/06/13 08:39:00 UTC
[jira] [Updated] (SLING-4804) Semicolon parameters are not passed
to the resource resolver
[ https://issues.apache.org/jira/browse/SLING-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomek Rękawek updated SLING-4804:
---------------------------------
Attachment: SLING-4804.patch
The attached patch adds the semicolon parameter back to the path in the {{RequestData#initResource()}}. It also adds an integration test that checks the semicolon parameters support using the {{;v=1.1}} to retrieve a historic resource.
> Semicolon parameters are not passed to the resource resolver
> ------------------------------------------------------------
>
> Key: SLING-4804
> URL: https://issues.apache.org/jira/browse/SLING-4804
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: Engine 2.4.2
> Reporter: Tomek Rękawek
> Assignee: Tomek Rękawek
> Priority: Minor
> Fix For: Engine 2.4.4
>
> Attachments: SLING-4804.patch
>
>
> SLING-848 provided a way to pass semicolon-separated parameters to the resource provider. However, such parameters are removed from the {{HttpServletRequest#getPathInfo()}}, which is used in the {{RequestData#initResource()}} method to resolve the resource from the URI. As a result, resource resolver and resource provider don't see the semicolon parameters and can't use them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)