[ 
https://issues.apache.org/jira/browse/CXF-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240048#comment-13240048
 ] 

Matt Parker edited comment on CXF-4207 at 3/27/12 11:27 PM:
------------------------------------------------------------

Thanks, using the properties you list, I have confirmed that this is a tomcat 
config issue and not a CXF issue.

Also, sorry for the misleading description--I am actually seeing 400, not 404. 
Had I mentioned that, it would have been more obvious what was happening. I'll 
update the description accordingly.

Thank you very much.
                
      was (Author: mparker):
    ALLOW_ENCODED_SLASH=true allows %2F as you say, thanks much. I still can't 
get %5C to work (I get 400 Invalid URI), but I suspect that to also be part of 
the container behavior and not part of CXF.

Also, sorry for the misleading description--I am actually seeing 400, not 404. 
Had I mentioned that, it would have been more obvious what was happening. I'll 
update the description accordingly.
                  
> CXF interprets URL-encoded slashes in PathParam prior to method dispatch
> ------------------------------------------------------------------------
>
>                 Key: CXF-4207
>                 URL: https://issues.apache.org/jira/browse/CXF-4207
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.4.2, 2.5.3
>            Reporter: Matt Parker
>
> For a method which handles, for example, "@Path(/rest/{value})": if either a 
> forward or backward slash is encoded and provided as part of "{value}", CXF 
> will interpret the encoded slash as a URI separator, rather than as a part of 
> "{value}".
> For example, "GET /rest/my%5Cvalue" will be interpreted as "GET 
> /rest/my\value" prior to dispatching, and will then fail with a 400 Invalid 
> URI, rather than passing "my\value" to the method handling the 
> "/rest/{value}" URI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to