How to test keep-alive is working?

2011-08-26 Thread bradford 
How do I test that keep-alive is working?

I've added option http-server-close to the frontend and do not see a
connection header in the http response.  I use to see connectino: closed
when I had httpclose enabled, but don't see connection: keep-alive or
anything similar.  So, how do I test it's working?

Bradford

Re: How to test keep-alive is working?

2011-08-26 Thread Bryan Talbot 
You could use something as simple as curl to see if the connection is left
in-tact.

$ curl -I -v www.example.com

If keep-alive is working, curl will include a verbose message like this:

* Connection #0 to host www.example.com left intact

and then close the connection since it has no pending requests to make

* Closing connection #0

-Bryan



On Fri, Aug 26, 2011 at 11:56 AM, bradford fingerm...@gmail.com wrote:

 How do I test that keep-alive is working?

 I've added option http-server-close to the frontend and do not see a
 connection header in the http response.  I use to see connectino: closed
 when I had httpclose enabled, but don't see connection: keep-alive or
 anything similar.  So, how do I test it's working?

 Bradford

Re: How to test keep-alive is working?

2011-08-26 Thread Baptiste 
Hi,

In HTTP 1.1,  Keep alive is the default mode and does not require any header.
On the other hand, in HTTP 1.0, there is no keepalive by default,
that's why browser and web servers had to anounce it.

More information available here:
http://blog.exceliance.fr/2011/06/30/implement_http_keepalive_without_killing_your_apache_server/

cheers


On Fri, Aug 26, 2011 at 8:56 PM, bradford fingerm...@gmail.com wrote:
 How do I test that keep-alive is working?

 I've added option http-server-close to the frontend and do not see a
 connection header in the http response.  I use to see connectino: closed
 when I had httpclose enabled, but don't see connection: keep-alive or
 anything similar.  So, how do I test it's working?

 Bradford