[
https://issues.apache.org/jira/browse/CAMEL-8774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544784#comment-14544784
]
Willem Jiang commented on CAMEL-8774:
-------------------------------------
I just found camel-http, camel-http4, camel-ahc have the same issue here.
> DefaultJettyHttpBinding preserves CONTEXT_ENCODING from the request even HTTP
> response doesn't contain the header
> -----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-8774
> URL: https://issues.apache.org/jira/browse/CAMEL-8774
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
> Affects Versions: 2.15.2
> Reporter: Mateusz Nowakowski
> Assignee: Willem Jiang
> Fix For: 2.14.3, 2.16.0, 2.15.3
>
>
> When Http Request is Gzip encoded (CONTENT_ENCODING is set) but the HTTP
> response is not (
> httpExchange.getResponseHeaders().get(HttpHeaders.CONTENT_ENCODING) == null)
> then Exchange.CONTENT_ENCODING is present in the Camel out message.
> This is because DefaultJettyHttpBinding:125 preserves all in headers.
> I believe that HTTP protocol headers (except custom ones) from the in
> shouldn't be copied to the Camel out message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
