You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Mateusz Nowakowski (JIRA)" <ji...@apache.org> on 2015/05/13 10:10:01 UTC

[jira] [Created] (CAMEL-8774) DefaultJettyHttpBinding preserves CONTEXT_ENCODING from the request even HTTP response doesn't contain the header

Mateusz Nowakowski created CAMEL-8774:
-----------------------------------------

             Summary: 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


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)