From: brian <brian@unknown>
Date: Sun, 22 Dec 1996 04:39:56 +0000 (+0000)
Subject: Clarify meaning of Timeout.
X-Git-Tag: APACHE_1_2b3~13
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9f12889cb0a04723006da7d65fec043178589b12;p=apache

Clarify meaning of Timeout.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77301 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html
index ba39c16782..91be55beb1 100644
--- a/docs/manual/mod/core.html
+++ b/docs/manual/mod/core.html
@@ -1101,12 +1101,22 @@ See also <A HREF="#minspareservers">MinSpareServers</A> and
 <strong>Context:</strong> server config<br>
 <strong>Status:</strong> core<p>
 
-The TimeOut directive sets the maximum time that the server will wait
-for the receipt of a request and the completion of a request, in seconds.
-So if it takes more than TimeOut seconds for a client to send a request or
-receive a response, the server will break off the connection. Thus TimeOut
-limits the maximum a transfer can take; for large files, and slow networks
-transfer times can be large.
+The TimeOut directive currently defines the amount of time Apache will
+wait for three things:
+
+<OL>
+  <LI>The total amount of time it takes to receive a GET request.
+  <LI>The amount of time between receipt of TCP packets on a POST or
+      PUT request.
+  <LI>The amount of time between ACKs on transmissions of TCP packets 
+      in responses.
+</OL>
+
+We plan on making these separately configurable at some point down the
+road.  1200 is very generous - you may consider turning it down to
+something smaller if you find the server getting swamped by
+half-completed connections from buggy browsers.
+
 <p><hr>
 
 <A name="user"><h2>User directive</h2></A>