camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10633) json dataformat should set a header "Content-Type: application/json" if there's no "Content-Type" header set
Date Fri, 23 Dec 2016 14:08:58 GMT

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

Claus Ibsen commented on CAMEL-10633:
-------------------------------------

There is a new contentTypeHeader which is default true for data formats which will tell the
data format to include that content type header if possible.

Then we can add logic to the various data formats to include the type, we likely need to allow
to do this in each implementation in case they need to set it specially.

> json dataformat should set a header "Content-Type: application/json" if there's no "Content-Type"
header set
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-10633
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10633
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: james strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.19.0
>
>
> if you marshal to json then send to a HTTP endpoint you'll be missing the fact that the
payload is now in JSON format. It seems a reasonable default to add this - so that a HTTP
endpoint can know it can parse the payload as JSON.
> e.g.
> {code}
> from("activemq:foo.bar").
>   to("dataformat:json-jackson:marshal").
>     /// TODO camel should now expose that the content type is json
>   to("http://foo.bar/")
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message