Stop decoding object content
Stop decoding object content

Previously, we had urllib3 (via requests) automatically decode all
responses with a Content-Encoding of deflate or gzip. This included
object downloads, which would in turn cause etag or content-length
mismatch errors. (See bug 1338464)

This was apparently added in response to a third-party proxy sitting
between the client and server which, having observed that the client
would accept gzip-encoded content while the server sent an unencoded
response, would perform the compression. (See bug 1282861)

Now, we'll no longer let requests send any default headers, nor do any
decoding.

Change-Id: I6cc30a5c12e37de06d7322533a3c36ad15397cc8
Closes-Bug: 1338464
Related-Bug: 1282861

ironsmile/python-swiftclient,sohonetlabs/python-swiftclient,sohonetlabs/python-swiftclient,openstack/python-swiftclient,VyacheslavHashov/python-swiftclient,jeseem/python-swiftclient,VyacheslavHashov/python-swiftclient,ironsmile/python-swiftclient,openstack/python-swiftclient,pratikmallya/python-swiftclient,pratikmallya/python-swiftclient,jeseem/python-swiftclient