Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What are some different ways/tools to verify that keep-alive is working on the server from the client's end?

share|improve this question
up vote 4 down vote accepted

You could try

ab -n 500 -c 5 -k http://www.domain.com/

and look via top, if 5 workers are constantly serving the requests keepalive should work (-k) switch. Do the same without -k and see the difference.

Cheers Izac

share|improve this answer
    
that's what i wound up doing, though i read that curl can tell you this too. if it says "Connection #0 to host www.example.com left intact", it means keep-alive is on. – Ron Garrity Aug 26 '11 at 20:53

As Ron Garrity says, you can use Curl like this:

curl -Iv http://www.aptivate.org 2>&1 | grep -i 'connection #0'

And it outputs these two lines if keep-alive is working:

* Connection #0 to host www.aptivate.org left intact
* Closing connection #0

And if keep-alive is not working, then it just outputs this line:

* Closing connection #0

The output Connection ... left intact proves that the server did not close the connection, and it is available for the client to reuse. It's up to the client to decide whether it actually wants to reuse the connection or not. You can demonstrate it with Curl by listing the same URL twice on the command line

curl -Iv http://www.aptivate.org --next http://www.aptivate.org 2>&1 | grep -i '#0'

in which case it will give output something like:

Re-using existing connection! (#0) with host ...
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.