What is a connection timeout during a http request

by

I will try to answer it a little bit more informally.

Connection timeout – is a time period within which a connection between a client and a server must be established. Suppose that you navigate your browser (client) to some website (server). What happens is that your browser starts to listen for a response message from that server but this response may never arrive for various reasons (e.g. server is offline). So if there is still no response from the server after X seconds, your browser will ‘give up’ on waiting, otherwise it might get stuck waiting for eternity.

Request timeout – as in the previous case where client wasn’t willing to wait for response from server for too long, server is not willing to keep unused connection alive for too long either. Once the connection between server and client has been established, client must periodically inform server that it is still there by sending information to that server. If client fails to send any information to server in a specified time, server simply drops this connection as it thinks that client is no longer there to communicate with it (why wasting resources meaninglessly).

Time to live (TTL) – is a value specified inside of a packet that is set when the packet is created (usually to 255) that tells how long the packet can be left alive in a network. As this packet goes through the network, it arrives at routers that sit on the path between the packet’s origin and its destination. Each time the router resends the packet, it also decrements its TTL value by 1 and if that value drops to 0, instead of resending the packet, router simply drops it as the packet is not supposed to live any longer. This mechanism is used to prevent network from flooding by data as each packet can live inside of it for only limited amount of ‘time’.

More Related Contents:

  1. How to set a timeout on a http.request() in Node?
  2. Where can I find the default timeout settings for all browsers?
  3. What is the maximum length of a URL in different browsers?
  4. What requests do browsers’ “F5” and “Ctrl + F5” refreshes generate?
  5. CORS with POSTMAN
  6. Detecting the character encoding of an HTTP POST request
  7. Is a 302 redirect to relative URL valid, or invalid?
  8. ETag vs Header Expires
  9. How can I get the clients IP address from HTTP headers?
  10. Java HTTP Client Request with defined timeout
  11. What is the limit on QueryString / GET / URL parameters
  12. What is the difference between URI, URL and URN? [duplicate]
  13. How many socket connections can a web server handle?
  14. Comparing HTTP and FTP for transferring files
  15. What are proper status codes for CORS preflight requests?
  16. REST response code for invalid data
  17. How big can a user agent string get?
  18. What rules apply to MIME boundary?
  19. How can I find out whether a server supports the Range header?
  20. REST, HTTP DELETE and parameters
  21. What is the boundary parameter in an HTTP multi-part (POST) Request?
  22. How to send NULL in HTTP query string?
  23. Semicolon as URL query separator
  24. Get client’s real IP address on Heroku
  25. How can I deal with HTTP GET query string length limitations and still want to be RESTful?
  26. HTTP Keep Alive and TCP keep alive
  27. How to serve http partial content with Go?
  28. Make a URL-encoded POST request using `http.NewRequest(…)`
  29. Can a http server detect that a client has cancelled their request?
  30. How does url rewrite works?

Leave a Comment