[
https://issues.apache.org/jira/browse/SLING-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725493#comment-14725493
]
Bertrand Delacretaz commented on SLING-4804:
--------------------------------------------
Well, if I understand [~tomek.rekawek] correctly our failure scenario is:
* Incoming request is like /foo;v=1.1
* The servlet engines' request.getRequestURI() returns /foo;v=1.1
* The Felix ServletRequestWrapper wraps that request object and its
getRequestURI() method returns /foo
If this scenario is correct I fail to see why ServletRequestWrapper modifying
that value is correct. Also as this IMO doesn't match the
HttpServletRequest.getRequestURI docs quoted above.
I would be ready to believe that this is not a bug, if you can provide some
justification to counter my hypothesis ;-)
> 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)
