[ 
https://issues.apache.org/jira/browse/CAMEL-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Beryozkin reopened CAMEL-5405:
-------------------------------------

    Estimated Complexity: Novice  (was: Unknown)

Propagating the actual Request URI causes the mis-match at the CXF level when 
Camel Servlet is also used. For example, Camel Servlet will set Request URI as 
"/webapp/HelloWorld", but also set the base URI as "servlet:///HelloWorld". 
To calculate the base address, CXF needs HttpServletRequest propagated too
                
> CXF Transport loses HTTP Matrix parameters
> ------------------------------------------
>
>                 Key: CAMEL-5405
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5405
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.9.2
>            Reporter: Sergey Beryozkin
>            Assignee: Willem Jiang
>             Fix For: 2.8.6, 2.9.3, 2.10.1
>
>         Attachments: camel5405.diff
>
>
> DefaultCxfMesssageMapper (note the typo - to be fixed in a follow-up JIRA) 
> wrongly initializes CXF Message Message.REQUEST_URI property with the value 
> of Camel Exchange.HTTP_PATH, even though Camel Exchange.HTTP_URI is available.
> The net effect is that the HTTP matrix parameters if any attached to the last 
> HTTP path segment are lost. Another side-effect is that Exchange.HTTP_PATH 
> will contain the decoded value (done at HTTPServletRequest level) which can 
> lead to the matching issues at the JAX-RS level.
> A simple patch is attached

--
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