[
https://issues.apache.org/jira/browse/HTTPCLIENT-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558238#comment-14558238
]
Michael Osipov commented on HTTPCLIENT-1651:
--------------------------------------------
That actually causes two questions:
1. If you use the {{HttpClientBuilder}} and provide both
{{RequestConfig#setContentCompressionDisabled(true)}} and
{{HttpClientBuilder#disableContentCompression}} which should be used?
2. If this is placed in {{RequestConfig}} that would mean that a client has to
create a {{RequestConfig}} instance, a {{HttpContext}} instance, put the config
into the context and run the appropriate execute method observing that the
config from context should not interfere with the config from the client
builder?
> 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
> Fix For: 4.5
>
>
> 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]
