CachingHttpClient should have similar behavior as AbstractHttpClient when
executing with ResponseHandler
--------------------------------------------------------------------------------------------------------
Key: HTTPCLIENT-1155
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1155
Project: HttpComponents HttpClient
Issue Type: Bug
Components: Cache
Affects Versions: 4.1.2, 4.2 Alpha2
Reporter: James Miller
When calling execute on the AbstractHttpClient with a ResponseHandler, the
AbstractHttpClient will attempt to Consume the Entity and close any open
connections before returning. This behavior is not currently in the
CachingHttpClient.
This can lead to connection leaks when switching to CachingHttpClient, becuase
the responsibility to fully consume the entity is now on the ResponseHandler
instead on the HttpClient.
Here is the code that does the existing 'auto-close' behavior:
"org.apache.http.impl.client.AbstractHttpClient.java" lines 1080-1111
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
