On Wed, Dec 19, 2018, 09:41 Khare, Aparna Dear All,
>
> We have some constraints in moving to new httpclient and we are using
> 4.1.3. Any help is appreciated. gzipContent works but deflated is not
> working.
>
> if (response.getEntity() != null) {
> HttpEntity entity =
Hi Paul,
Depending on exactly what timeouts you need to change dynamically, maybe you
can use RequestConfig to set it per request instead of per Client?
If not, you could override PoolingHttpClientConnectionManager, add a
shutdown flag, and override releaseConnection, so that if this flag is
Hi Francois,
I believe the problem is that the implementation of awaitTermination in Java
requires that the amount of time in *nanoseconds* is no more than
Long.MAX_VALUE. This has nothing to do with HC.
To get the maximum possible delay, just do
server.awaitTermination(Long.MAX_VALUE,
This is supposed to work out of the box.
My suggestion would be to remove the setHttpProcessor call, remove all the
addHeader calls (but pass the content type to the StringEntity creation), as
the necessary headers are added automatically, and see what happens. If it
still doesn't work I would
Use HttpClientBuilder.setDefaultRequestConfig:
https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/impl/client/HttpClientBuilder.html#setDefaultRequestConfig(org.apache.http.client.config.RequestConfig).
With RequestConfig.Builder.setLocalAddress
Hi,
I know this is an old subject, and related to the closed tickets
https://issues.apache.org/jira/browse/HTTPCLIENT-1204 and
https://issues.apache.org/jira/browse/HTTPCLIENT-1392, but it seems to be a
different case, and I’m not even sure it is not a bug.
If you go to some sites with an
