[
https://issues.apache.org/jira/browse/CAMEL-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149149#comment-14149149
]
Yaron A commented on CAMEL-7848:
--------------------------------
Indeed.
The current HttpClientPipelineFactory does not respect the Content-Encoding
header.
So if for instance, the response contains Content-Encoding = gzip, the body
won't get decompressed.
I managed to solve it by writing my own custom ClientPipelineFactory that does
take into account the encoders/decoders, and then I added the
HttpContentDecompressor as a decoder in order to solve the issue.
Thanks
> Netty-Http component: add support for registry's encoders and decoders
> ----------------------------------------------------------------------
>
> Key: CAMEL-7848
> URL: https://issues.apache.org/jira/browse/CAMEL-7848
> Project: Camel
> Issue Type: New Feature
> Components: camel-netty-http
> Affects Versions: 2.14.0
> Reporter: Yaron A
> Assignee: Willem Jiang
>
> Currently the camel-netty component supports setting encoders & decoders that
> enlisted in the registry.
> It will be very helpful to have this functionality similarly supported in the
> camel-netty-http component too.
> From what I saw, camel-netty's ClientPipelineFactory implementation
> (DefaultClientPipelineFactory) supports it in the getPipeline method but a
> similar implementation does not exist in camel-netty-http's
> ClientPipelineFactory implementation (HttpClientPipelineFactory).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
