You are viewing a plain text version of this content. The canonical link for it is here.
Posted to httpclient-users@hc.apache.org by Oleg Kalnichevski <ol...@apache.org> on 2006/05/24 23:20:58 UTC

Re: Handling HTTP Keep-Alives

On Wed, 2006-05-24 at 15:16 -0500, John Corro wrote:
>   I've been noticing that I'm receiving Keep-Alive headers from a server I'm trying to access.  I was looking for any built-in methods that will tell me the status of this header flag and the closest thing I could find was "HttpMethodBase.shouldCloseConnection()", but that's protected.  Is there a specific reason this isn't given a "public" scope?  
> I would like to be able to tell if a connection should be kept alive or not (without manually having to look for the header, etc) so that I don't explicitly close it via a "releaseConnection()" when I've completed executing the http call.  To the best of my knowledge a call to "releaseConnection()" will cause the connection to close without regard of any Keep-Alive header values - please correct me if this understanding is wrong.

John,

HttpClient always keeps connection open per default if they can be kept
alive. Please consider implementing a custom connection manager if you
want to exert a greater control over the connection management process.

Hope this helps

Oleg


>  
> 
> John M. Corro
> www.cornerstone.net
> Cornerstone Consulting, Inc
> 731 N. Jackson Street, Suite 600 
> Milwaukee, WI 53202
> (414) 212-3500


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