Just replied on stackoverflow.
Marek
On 05 Nov 2013, at 17:50, Rafael Winterhalter <Rafael.Winterhalter_at_kantega.no> wrote:
> Can anybody explain why Jersey swallows my «Content-Encoding» header? If I set the header programmatically via Jersey-Client, e.g:
>
> target().request().header(“Content-Encoding”, “my-encoding”).post()
>
> The “Content-Encoding” header does not “make it” to the server. It is not even visible in the request dump. I posted a runnable example of this behavior on Stack Overflow.
>
> http://stackoverflow.com/questions/19794014/why-does-jersey-swallow-my-content-encoding-header
>
> How can I turn this off? I really need to handle the “Content-Encoding” myself.
>
> Thank you for your help.
> Best, Rafael