[
https://issues.apache.org/jira/browse/SLING-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725376#comment-14725376
]
Bertrand Delacretaz commented on SLING-4804:
--------------------------------------------
Do we know what the correct behavior is supposed to be?
http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getRequestURI%28%29
says _returns the part of this request's URL from the protocol name up to the
query string in the first line of the HTTP request. The web container does not
decode this String_
My understanding is that in a URL like /foo;v=1.1?x=y the ;v=1.1 should be
included in getRequestURI()
I'm not trying to be pedantic, just trying to make sure we're not chasing the
wrong bugs. If the reality if that different servlet engines each interpret
this in their own way we might need some clever fallbacks, which is IIUC what
[~tomek.rekawek] is creating here?
> 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)
