[CAMEL-10123] gzip added to Accept-Encoding although not requested

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 2.17.1
• Component/s: camel-jetty
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Rudolf Batt
• Created: 05/Jul/16 14:49
• Updated: 06/Aug/19 08:18
• Resolved: 06/Aug/19 08:18

Description

I have a standard proxy route using the camel-jetty component:

<route>
<from uri="jetty:http://0.0.0.0:8082/docs?matchOnUriPrefix=true"/>
<to uri="jetty:http://127.0.0.1:8080/docs?bridgeEndpoint=true&amp;throwExceptionOnFailure=false" />
<route>

The Problem is this: If a request is send to the proxy (8082) with the HTTP header "Accept-Encoding: deflate"

curl -s -v -H 'Accept-Encoding: deflate' 'http://localhost:8082/docs/setup.html' -o /dev/null

the "backend server" receives a request with the header "Accept-Encoding: gzip,deflate".

This would be OK, if the compression is "terminated" at the communication to the client. However if the "backend server" returns gzipped content (marking it with the response header "Content-Encoding: gzip"), the proxy returns that header as well, although no compression is done:

I can see that, because I get a "Exception: Not in GZIP format" in my Java Client. Also comparing the downloaded size with my curl command (

--write-out 'size_download=%{size_download}\n'

) reveals the fact, that the response is not compressed.

(I'll post my workaround, as soon as I found it. I guess I have to use a GZipHandler..)