Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-8774

DefaultJettyHttpBinding preserves CONTEXT_ENCODING from the request even HTTP response doesn't contain the header

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.15.2
    • 2.14.3, 2.15.3, 2.16.0
    • camel-jetty
    • None
    • Unknown

    Description

      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.

      Attachments

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            njiang Willem Jiang
            matihost Mateusz Nowakowski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment