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] [Updated] (CAMEL-5806) DefaultHttpBinding shouldn't assume null payload if HttpMethod == GET
Date Mon, 16 Feb 2015 13:05:12 GMT

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

Claus Ibsen updated CAMEL-5806:
-------------------------------
    Component/s: camel-jetty
                 camel-http4

> DefaultHttpBinding shouldn't assume null payload if HttpMethod == GET
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-5806
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5806
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-http, camel-http4, camel-jetty
>            Reporter: Raúl Kripalani
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.15.0
>
>
> Jetty Consumer: DefaultHttpBinding#parseBody inserts a null body into the message if
the incoming request is for HTTP Method GET.
> If I'm not mistaken, according to the HTTP spec the payload is only null if the Content-Length
header is 0 or if it doesn't exist. Hence, we have a shortcoming in the Camel HTTP components.
> Even though it's unusual, there are reasons why a client could send payload with a GET
request. Take a look at the [search operation|http://www.elasticsearch.org/guide/reference/api/search/]
in the Elastic Search API, as an example.



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

Mime
View raw message