[
https://issues.apache.org/jira/browse/SLING-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591768#comment-14591768
]
Carsten Ziegeler commented on SLING-4804:
-----------------------------------------
[~tomek.rekawek] I couldn't come up with a good solution either, in my case we
just decided to ignore path parameters as Jetty (or Jetty's getPathInfo) does.
I guess there will be servlet engines which provide path parameters as part of
getPathInfo and others which don't (like Jetty).
The patch looks basically good to me, however, could it be improved by first
checking whether getRequestURI contains a semicolon and only do the decoding if
it has one? And of course only if getPathInfo doesn't have it?
> 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.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)
