[issue26231] HTTPResponse.close() should consume all remaining data in body if any

Irit Katriel added the comment: > If close() does not consume the remaining data, the user would have to do it > after invoking close(), regardless of how large the data is. Martin's point was that you can abandon the connection and create a new one if you choose not to consume all the data

[issue26231] HTTPResponse.close() should consume all remaining data in body if any

Jacky added the comment: In my opinion, HTTPResponse.close() should do really close work. Not only releasing the underlying file obj but also need to consume the remaining data to make sure the request complete. If close() does not consume the remaining data, the user would have to do it afte

[issue26231] HTTPResponse.close() should consume all remaining data in body if any

New submission from Jacky: HTTPResponse.close() in httplib should consume all remaining data in body if any. Or the followed request would get the unread content from the previous request, which result in the wrong result. The following code shown that the second request will get a wrong statu

[issue26231] HTTPResponse.close() should consume all remaining data in body if any

Martin Panter added the comment: The documentation already says you have to read the whole response before sending a new request: . So I think this is more like a new feature than a bug fix, and would have to g