[
https://issues.apache.org/jira/browse/CAMEL-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380217#comment-14380217
]
Ralf Steppacher commented on CAMEL-7638:
----------------------------------------
Is this ticket somewhere on the roadmap? It would be extremely beneficial to my
project if this could be implemented.
Another thing I noticed in this context: The netty4-http component currently
re-calculates the content length of a response if used in a proxy route. And it
seems I have no control over the headers, that is I cannot switch to chunked
transfer encoding if I massage the response stream contents in a streaming
fashion. I came across at least one recent ticket that was about expected
content length/transfer encoding headers in proxy setups.
> Use response input stream directly in http producer
> ---------------------------------------------------
>
> Key: CAMEL-7638
> URL: https://issues.apache.org/jira/browse/CAMEL-7638
> Project: Camel
> Issue Type: Improvement
> Reporter: Willem Jiang
> Assignee: Willem Jiang
>
> It could save us lots of the memory and time if the response is a big and
> chunked message.
> Here are some discussion in the mailing list about it.
> http://camel.465427.n5.nabble.com/Stream-only-reverse-proxy-with-minimal-memory-footprint-tp5754424.html
>
> http://camel.465427.n5.nabble.com/Chunking-issue-with-http-producer-td5735075.html
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
