HTTP Keep Alive and TCP keep alive

by

I know this is an old question, but still:

  • HTTP Keep-Alive is a feature that allows HTTP client (usually browser) and server (webserver) to send multiple request/response pairs over the same TCP connection. This decreases latency for 2nd, 3rd,… HTTP request, decreases network traffic and similar.

  • TCP keepalive is a totally different beast. It keeps TCP connection opened by sending small packets. Additionally, when the packet is sent this serves as a check so the sender is notified as soon as connection drops (note that this is NOT the case otherwise – until we try to communicate through TCP connection we have no idea if it is ok or not).

To answer your questions about HTTP Keep-Alive:

How is HTTP Keep Alive implemented?

To put it simply, the HTTP server doesn’t close the TCP connection after each response but waits some time if some other HTTP request will come over it too. After some timeout it closes it anyway.

Does it internally use TCP Keep Alive?

No, at least I see no point in it.

If not, how does the server detect if the client is dead or alive?

It doesn’t – it doesn’t need to. If a client sends a request, it will get the response. If the client doesn’t send anything over TCP connection (maybe because the connection is dead) then a timeout will close the connection; client will of course notice this and will send request through another TCP connection if needed.

More Related Contents:

  1. How do multiple clients connect simultaneously to one port, say 80, on a server? [duplicate]
  2. How many socket connections can a web server handle?
  3. What is the difference between a URI, a URL and a URN?
  4. Can I read the hash portion of the URL on my server-side application (PHP, Ruby, Python, etc.)?
  5. Are the PUT, DELETE, HEAD, etc methods available in most web browsers?
  6. Is an entity body allowed for an HTTP DELETE request?
  7. Are HTTP headers case-sensitive?
  8. Does a TCP socket connection have a “keep alive”?
  9. How to display the Authentication Challenge in UIWebView?
  10. Difference between Pragma and Cache-Control headers?
  11. Why both no-cache and no-store should be used in HTTP response?
  12. How to make an HTTP request from SSIS?
  13. server socket receives 2 http requests when I send from chrome and receives one when I send from firefox
  14. Returning http 200 OK with error within response body
  15. HTTP status code 0 – Error Domain=NSURLErrorDomain?
  16. URL without “http|https”
  17. What is q=0.5 in Accept* HTTP headers?
  18. Basic static file server in NodeJS
  19. Are Callable Cloud Functions better than HTTP functions?
  20. What’s the correct encoding of HTTP get request strings?
  21. Orchestrating microservices
  22. Angular2 / Error: Collection not found
  23. Add subdomain to localhost URL
  24. Basic HTTP authentication in Node.JS?
  25. HTTP Cache Control max-age, must-revalidate
  26. Are JSON web services vulnerable to CSRF attacks?
  27. Is an HTTP PUT request required to include a body?
  28. http download file name
  29. how can an application use port 80/HTTP without conflicting with browsers?
  30. How does url rewrite works?

Leave a Comment