[ https://issues.apache.org/jira/browse/CAMEL-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914353#comment-13914353 ]
Sergey Beryozkin edited comment on CAMEL-7246 at 2/27/14 10:22 AM: ------------------------------------------------------------------- Hi Raul, Do you think we can block the copying of the input Content-Type to the output *by default*, without having to start blocking the whole headers via the header strategy, when the Content-Type of the response is already available ? This can be checked on the CXF exchange, exchange.get(org.apache.cxf.message.Message.CONTENT_TYPE) ? Otherwise we have the side-effects, like the one in the attached test, and another one when we have a wildcard Content-Type in GET requests, this wildcard (\*/\*) overrides the Content-Type of the response derived from @Produces Thanks, Sergey was (Author: sergey_beryozkin): Hi Raul, Do you think we can block the copying of the input Content-Type to the output *by default*, without having to start blocking the whole headers via the header strategy, when the Content-Type of the response is already available ? This can be checked on the CXF exchange, exchange.get(org.apache.cxf.message.Message.CONTENT_TYPE) ? Otherwise we have the side-effects, like the one in the attached test, and another one when we have a wildcard Content-Type in GET requests, this wildcard (*/*) overrides the Content-Type of the response derived from @Produces Thanks, 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.1.5#6160)