[
https://issues.apache.org/jira/browse/CXF-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976859#action_12976859
]
Sergey Beryozkin commented on CXF-3226:
---------------------------------------
Hi
But what happens if you have "the%20%space" Path value or similar ? If we
decode at the servlet level then we won't be able to match "the%20%space" ?
Can JAX-RS Path can not contain WSPaces in the actual literal name ? Do you
think this is still a valid JIRA ?
thanks, Sergey
> Going to a JAX-RS resource that contains a space in the path returns a 404
> response code
> ----------------------------------------------------------------------------------------
>
> Key: CXF-3226
> URL: https://issues.apache.org/jira/browse/CXF-3226
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.3.1
> Environment: Java 1.6_22
> Apache CXF 2.3.1
> Reporter: Jason Downey
> Fix For: 2.3.2
>
> Attachments: cxf_jax_rs_space_bug.zip, patch.diff
>
>
> If you go to a JAX-RS resource that contains a space in the path, the Apache
> CXF JAX-RS runtime returns a 404 response code. In the STDERR log, you'll see
> the following message:
> Jan 1, 2011 3:05:01 PM org.apache.cxf.jaxrs.utils.JAXRSUtils findTargetMethod
> WARNING: .No operation matching request path /has%20space is found, HTTP
> Method : GET, ContentType : */*, Accept :
> application/xml,application/xhtml+xml,image/png,text/html;q=0.9,text/plain;q=0.8,*/*;q=0.5,.
> The cause for this problem may be found in
> AbstractServerController.getBaseURL. It assumes pathInfo is always decoded
> but in the JAX-RS situation, it may actually still be encoded.
> Relevant sample code + patch attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
