You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by bu...@apache.org on 2006/03/17 15:48:07 UTC

DO NOT REPLY [Bug 39014] - HTTP Client 3.0 doesn't close sockets

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39014>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39014


odi@odi.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From odi@odi.ch  2006-03-17 14:48 -------
It's a feature, not a bug. Of course releaseConnection() doesn't imply the
socket is closed. HttpClient manages a connection pool even with the simple
connection manager. If you want your sockets to close immediately, include a
"Connection: close" header in your request or resort to HTTP/1.0. You may also
call HttpConnectionManager.closeIdleConnections(0).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org