slive 00/10/23 15:38:15
Modified: htdocs/manual/mod core.html
Log:
One more update that Jim forgot for the "config directory" patch.
Plus, get rid of links to the obsolete and redundant keepalive.html.
Instead, include the information with the directive.
Revision Changes Path
1.176 +36 -11 httpd-docs-1.3/htdocs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/core.html,v
retrieving revision 1.175
retrieving revision 1.176
diff -u -r1.175 -r1.176
--- core.html 2000/10/06 00:53:14 1.175
+++ core.html 2000/10/23 22:38:14 1.176
@@ -1279,6 +1279,11 @@
This directive allows inclusion of other configuration files from within the
server configuration files.
+<P>New in Apache 1.3.13 is the feature that if <CODE>Include</CODE>
+points to a directory, rather than a file, Apache will read all
+files in that directory, and any subdirectory, and parse those
+as configuration files.
+
<P> <HR>
<H2><A NAME="keepalive">KeepAlive directive</A></H2>
@@ -1300,18 +1305,32 @@
><STRONG>Compatibility:</STRONG></A> KeepAlive is only available in Apache
1.1 and later.<P>
-This directive enables
-<A HREF="../keepalive.html">Keep-Alive</A>
-support.
+<p>The Keep-Alive extension to HTTP/1.0 and the persistent connection
+feature of <CODE>HTTP/1.1</CODE> provide long-lived HTTP sessions
+which allow multiple requests to be sent over the same TCP connection.
+In some cases this been shown to result in an almost 50% speedup in
+latency times for HTML documents with many images.</p>
+
+<p>In order for Keep-Alive support to be used:
+<ul>
+<li>Keep-Alive support must be enabled by setting this directive
+to <code>On</code>.</li>
+<li>The client must support Keep-Alive requests. Most current
+clients do support Keep-Alive requests.</li>
+<li>The length of the file must be know in advance. This means that most
+CGI scripts, server-parsed pages (SSI), and server-generated directory
+listings, will not use the Keep-Alive protocol.</li>
+</ul>
<P><STRONG>Apache 1.1</STRONG>: Set <EM>max-requests</EM>
to the maximum number of requests you want Apache to entertain per
request. A limit is imposed to prevent a client from hogging your
server resources. Set this to <CODE>0</CODE> to disable support.
+
+<p>See also <A
+HREF="#maxkeepaliverequests">MaxKeepAliveRequests</A>.</P>
-<P><STRONG>Apache 1.2 and later</STRONG>: Set to "On" to enable
-persistent connections, "Off" to disable. See also the <A
-HREF="#maxkeepaliverequests">MaxKeepAliveRequests</A> directive.</P><HR>
+<HR>
<H2><A NAME="keepalivetimeout">KeepAliveTimeout directive</A></H2>
<A
@@ -1335,12 +1354,18 @@
REL="Help"
><STRONG>Compatibility:</STRONG></A> KeepAliveTimeout is only available in
Apache 1.1 and later.<P>
+
+<p>The number of seconds Apache will wait for a subsequent request
+before closing the connection. Once a request has been received, the
+timeout value specified by the <A
+HREF="#timeout"><CODE>Timeout</CODE></A> directive applies.</p>
+
+<p>Setting <code>KeepAliveTimeout</code> to a high value may
+cause performance problems in heavily loaded servers. The
+higher is the timeout, the more server processes will be kept
+occupied waiting on connections with idle clients.</p>
+
-The number of seconds Apache will wait for a subsequent request before
-closing the connection. Once a request has been received, the timeout
-value specified by the <A
-HREF="#timeout"><CODE>Timeout</CODE></A> directive
-applies.
<HR>
<H2><A NAME="limit"><Limit> directive</A></H2>
