[
https://issues.apache.org/jira/browse/SLING-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726941#comment-14726941
]
Bertrand Delacretaz commented on SLING-4804:
--------------------------------------------
Thanks - now that we have a clear explanation I agree that using
{{getRequestURL}} makes sense.
I have created SLING-4987 to upgrade to org.apache.felix.http.jetty/3.1.0 and
adapt the affected tests accordingly.
> 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-2.patch, SLING-4804-3.patch, 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)
