How to test HTTP Keep alive is actually working

http wireshark keep-alive
sub picture sub · Nov 22, 2010 · Viewed 14.1k times · Source

I know HTTP keep-alive is on by default in HTTP 1.1 but I want to find a way to confirm that it is actually working.

Does anyone know of a simple way to test from a web browser (EG how to make sense of wireshark). I know I need to look for multiple HTTP requests over the same TCP connection but I don't know how to confirm that in wireshark or any other way.

Thanks!

Answer

qris picture qris · Nov 13, 2013

As Ron Garrity said on ServerFault, 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

Related questions

Sniff HTTP packets for GET and POST requests from an application

I am coding an SEO tool in C# for doing keyword research. I need to make calls to Google Adword keyword tool. Now I know some tools which are doing the same already. I just need to decipher what they …

Read More
How do I monitor all incoming http requests?

I need to monitor my application from incoming http POST and GET requests originating from outside and sometimes inside the machine. Is this possible? Been using fiddler but this only does outgoing not incoming (from outside the machine) or have …

Read More
Wireshark filter for filtering both destination-source IP address and the protocol

I want to filter Wireshark's monitoring results according to a filter combination of source, destination ip addresses and also the protocol. So, right now I'm able to filter out the activity for a destination and source ip address using this …

Read More