[
https://issues.apache.org/jira/browse/HTTPCLIENT-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565084#comment-14565084
]
Michael Osipov commented on HTTPCLIENT-1651:
--------------------------------------------
Sorry, I cannot follow you. Which can be handled this way? Neither
{{contentCompressionEnabled}} nor {{contentDecompressionEnabled}} can, can
they? We have code which is in place and fully working already. All we can do
now is give more control over compression and decompression.
> Add ability to disable content compression on a request basis
> -------------------------------------------------------------
>
> Key: HTTPCLIENT-1651
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1651
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Affects Versions: 4.4.1
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Fix For: 4.5, 5.0
>
>
> We use one client for serveral, different requests. Most of the are
> {{application/xml}} where compression is appropriate but some transport big
> binary data. Those requests drop from 30 MB/s to 5 to 7 MB/s.
> Unfortunately, compression can only be disabled client-wide. A
> {{RequestConfig}} or {{HttpContext}} boolean flag for
> {{RequestContentEncoding}} processor would be great.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
