hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Should DefaultHttpClient add ResponseContentEncoding response handler as default?
Date Thu, 07 Apr 2011 00:18:11 GMT
The DefaultHttpClient class sets up a lot of HttpResponseInterceptors,
but does not currently include ResponseContentEncoding which handles
Content-Encoding (e.g. gzip)

Seems like a strange omission.

Its subclass ContentEncodingHttpClient adds ResponseContentEncoding,
but also adds RequestAcceptEncoding which might not be wanted for all
requests.

For example, JMeter creates an HttpClient instance, and may or may not
add the Accept-Encoding header later. So it has to sub-class
DefaultHttpClient to add the handler.

Would there be any drawback to including ResponseContentEncoding in
DefaultHttpClient by default?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message