[jira] [Comment Edited] (CAMEL-8169) Camel Jetty/Http4 producers should respect Content-Length/Transfer-Encoding:Chunked headers

["Willem Jiang (JIRA)" <ji...@apache.org>]

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

Willem Jiang edited comment on CAMEL-8169 at 12/29/14 6:16 AM:
---------------------------------------------------------------

We need to pass the Content-Length header to the Jetty/Http4 producers when the message body is Stream.
Applied the patch into camel master, camel-2.14.x and camel-2.13.x branches.


was (Author: njiang):
We need to pass the Content-Length header to the Jetty/Http4 producers when the message body is Stream.

> Camel Jetty/Http4 producers should respect Content-Length/Transfer-Encoding:Chunked headers
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-8169
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8169
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http4, camel-jetty
>    Affects Versions: 2.13.3, 2.14.1
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.13.4, 2.14.2, 2.15.0
>
>
> If Camel is used the HTTP proxy, users expect that Content-Length and Transfer-Encoding: Chunked headers should be respected when incoming request is redirected using HTTP4 or Jetty producers.
> If example if I send request to the following route...
> {code}
> from("servlet://0.0.0.0:8080").to("http4://foo.com"); 
> {code}
> ...and this request contains Content-Length header (and doesn't contain Transfer-Encoding: Chunked header) then request forwarded to foo.com should not be chunked. In Fuse 6.1 Camel will chunk frowarded request.
> In general client sending request to the Camel proxy gateway, should be sure that by default Camel will keep the same chunking/nonchunking behavior as specified in the original request.



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