Comment 3 for bug 1594739

I ran into a similar issue on the feature/crypto-review branch with review https://review.openstack.org/#/c/328204, but in that case the backend connections were not being closed for a non-MIME Putter. In the end I tracked that down to there being a reference held to the response object, so even though httplib.HTTPConnection.close() was being called by the proxy object controller, the object server was still waiting to read for 60 secs.

The patch attached is for master (diff against commit 84a8465) but uses similar solution that I intend to propose for https://review.openstack.org/#/c/328204. It will need tests adding but first we should decide on the right approach vs Kota's patch or another.

If I understand Kota's patch at #1, the sender (proxy) is deliberately provoking a MIME read error to cause the object server to stop waiting on a read. It may be that the underlying issue is the same as I have seen on feature/crypto-review, and actually the connection could just be closed without sending any bytes if the response reference was not being held.