[
https://issues.apache.org/jira/browse/CAMEL-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029076#comment-14029076
]
Sergey Beryozkin commented on CAMEL-7246:
-----------------------------------------
Hi Aki,
The problem with Content-Type is that when Simple binding is enabled, it
interferes with un-setting the correct output Content-Type already set by the
JAX-RS runtime, in cases where we have some kind of HTTP-level negotiation
going on.
So yes, I can understand that the original request Content-Type or
Content-Length may need to be visible to the rest of the route. But having such
headers copied to outbound CXF message by default is an issue as it is breaking
the original consumers who made the request and expect the data back. The fact
that it's not happening with the default binding suggests it is specific to
Simple Binding only
Cheers, Sergey
> [cxfrs] SimpleConsumer returns wrong Content-Type
> -------------------------------------------------
>
> Key: CAMEL-7246
> URL: https://issues.apache.org/jira/browse/CAMEL-7246
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.12.2
> Reporter: Alexey Markevich
> Attachments: camel-cxfrs-content-type.zip
>
>
> Looks like Content-Type is taken from request
--
This message was sent by Atlassian JIRA
(v6.2#6252)
