Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Apache got a parameter called Timeout.</p> <p>Its manual page ( <a href="http://httpd.apache.org/docs/2.2/mod/core.html#timeout" rel="nofollow">Apache Core - Timeout Directive</a> ) states:</p> <blockquote> <p>The TimeOut directive defines the length of time Apache will wait for I/O in various circumstances:</p> <ol> <li>When reading data from the client, the length of time to wait for a TCP packet to arrive if the read buffer is empty.</li> <li>When writing data to the client, the length of time to wait for an acknowledgement of a packet if the send buffer is full.</li> <li>In mod_cgi, the length of time to wait for output from a CGI script.</li> <li>In mod_ext_filter, the length of time to wait for output from a filtering process.</li> <li>In mod_proxy, the default timeout value if ProxyTimeout is not configured.</li> </ol> </blockquote> <p>I think you fell into case <strong>NUMBER ONE</strong></p> <p><strong>EDIT</strong></p> <p>I was lurking into W3 HTTP document and I found no refer to timeouts.</p> <p>but into the chapter 8 (connections) I found:</p> <p><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8" rel="nofollow">8.1.4 Practical Considerations</a></p> <p><em>Servers will <strong>usually</strong> have some time-out value beyond which they will no longer maintain an inactive connection. (...) The use of persistent connections places no requirements on the length (or existence) of this time-out for either the client or the server.</em></p> <p>that sounds to me like "every server or client is free to choose his behaviour about inactive connection timeouts"</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload