[ 
http://issues.ops4j.org/browse/PAXWEB-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907#action_13907
 ] 

Achim Nierbeck commented on PAXWEB-108:
---------------------------------------

Fixfor trunk (1.1.0): 
https://github.com/ops4j/org.ops4j.pax.web/commit/1b37de9b9f5798fe5281e34e95a2e149e3c9aa41

> Registering a servlet at "/" causes incorrect setting of servlet path and 
> path info on request
> ----------------------------------------------------------------------------------------------
>
>                 Key: PAXWEB-108
>                 URL: http://issues.ops4j.org/browse/PAXWEB-108
>             Project: Pax Web
>          Issue Type: Bug
>          Components: Http Service
>    Affects Versions: 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.3.0, 0.3.1, 0.4.0, 0.4.1, 
> 0.5.0, 0.5.1
>            Reporter: Niclas Hedhman
>            Assignee: Achim Nierbeck
>             Fix For: 1.0.2, 1.1.0
>
>
> When a request of "/api/foo/bar" is made which matches to a servlet 
> registered at "/api" the servlet path is correctly set as "/api" and the path 
> info set to "/foo/bar".  However if the same servlet is registered in exactly 
> the same manner to "/" and a request is made to "/foo/bar" the servlet path 
> is set to "/foo/bar" and the path info is null.  The servlet is somehow being 
> treated as though it was mounted against the exact uri that is being 
> requested no matter what that uri is.
> Bryce Ewing

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to