[
https://issues.apache.org/jira/browse/CAMEL-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602975#comment-16602975
]
ASF GitHub Bot commented on CAMEL-12751:
----------------------------------------
bobpaulin commented on issue #2496: CAMEL-12751 - Added Content-Length Test for
incorrect length.
URL: https://github.com/apache/camel/pull/2496#issuecomment-418345493
Agree the HttpComponents are a bit tricky. It appears that content-length
is already being filtered out properly in the
org.apache.camel.http.common.HttpHeaderFilterStrategy. The issue appears to be
that the filter did not work when the HttpRequestBase entity is a
InputStreamEntity since then the http-components is setting the content-length
on that object before the filter is applied. So it's sneaking through.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> http producer - Ignore content length header
> --------------------------------------------
>
> Key: CAMEL-12751
> URL: https://issues.apache.org/jira/browse/CAMEL-12751
> Project: Camel
> Issue Type: Improvement
> Components: camel-http, camel-http4
> Reporter: Claus Ibsen
> Priority: Major
>
> When doing eg REST -> HTTP etc then the REST consumer may populate the
> message with Content-Length header, which gets propagated to the http
> producer. We should by default ignore those existing headers and calculate
> the length in the producer based on the message body, eg if string, byte[]
> etc which AFAIR does today.
> See nabble
> http://camel.465427.n5.nabble.com/Content-Length-Header-being-used-previous-HTTP-Response-td5813376.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
