loopj/android-async-http — pull request #583 by ecdpalma (2014-06-03 02:04:08+00:00)
Title: Check if entity's stream is really compressed.

(I know this use case is absolutely uncommon, but maybe someone may need the same thing.)

One of our clients has a server returning 404 errors with
Content-Encoding=gzip, but the content itself is not compressed, causing
'new GZIPInputStream' in InflatingEntity#getContent to throw an
IOException.

When using FileAsyncHttpResponseHandler, for some reason we couldn't
find out, after some requests with the wrong 404 response,
AsyncHttpClient was getting stuck and after some time it raised
ConnectionPoolTimeoutException. This wasn't happening when the
BaseJsonHttpResponseHandler was being used.