Home/ Questions/Q 776653
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T19:28:59+00:00

I am trying to understand the relation between TCP/IP and HTTP timeout values. Are

  • 0

I am trying to understand the relation between TCP/IP and HTTP timeout values. Are these two timeout values different or same? Most Web servers allow users to set the HTTP Keep Alive timeout value through some configuration. How is this value used by the Web servers? is this value just set on the underlying TCP/IP socket i.e is the HTTP Keep Alive timeout and TCP/IP Keep Alive Timeout same? or are they treated differently?

My understanding is (maybe incorrect):
The Web server uses the default timeout on the underlying TCP socket (i.e. indefinite) regardless of the configured HTTP Keep Alive timeout and creates a Worker thread that counts down the specified HTTP timeout interval. When the Worker thread hits zero, it closes the connection.

EDIT:
My question is about the relation or difference between the two timeout durations i.e. what will happen when HTTP keep-alive timeout duration and the timeout on the Socket (SO_TIMEOUT) which the Web server uses is different? should I even worry about these two being same or not?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    They’re two separate mechanisms; the name is a coincidence.

    HTTP keep-alive (also known as persistent connections) is keeping the TCP socket open so that another request can be made without setting up a new connection.

    TCP keep-alive is a periodic check to make sure that the connection is still up and functioning. It’s often used to assure that a NAT box (e.g., a DSL router) doesn’t “forget” the mapping between an internal and external ip/port.

    • 0