Currently if the response entity isn't consumed or if exhaust() isn't called explicitly, the connection is blocked.
The idea is to have a default setting that would automatically exhaust() the entity upon release() of the ClientResource. Note that today we only keep track of the latest response, not the history of all calls.
Reported by @stoffeg
Currently if the response entity isn't consumed or if exhaust() isn't called explicitly, the connection is blocked.
The idea is to have a default setting that would automatically exhaust() the entity upon release() of the ClientResource. Note that today we only keep track of the latest response, not the history of all calls.
Reported by @stoffeg