Return-Path: Delivered-To: apmail-apache-cvs-archive@apache.org Received: (qmail 76222 invoked by uid 500); 23 Oct 2000 22:42:00 -0000 Mailing-List: contact apache-cvs-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-cvs@apache.org Received: (qmail 76197 invoked by uid 500); 23 Oct 2000 22:41:59 -0000 Delivered-To: apmail-apache-2.0-cvs@apache.org Delivered-To: apmail-httpd-docs-2.0-cvs@apache.org Date: 23 Oct 2000 22:41:58 -0000 Message-ID: <20001023224158.76187.qmail@locus.apache.org> From: slive@locus.apache.org To: httpd-docs-2.0-cvs@apache.org Subject: cvs commit: httpd-docs-2.0/htdocs/manual/mod core.html slive 00/10/23 15:41:58 Modified: htdocs/manual/mod core.html Removed: htdocs/manual keepalive.html Log: One more update for "config directory" patch, plus update of keep-alive documentation. Revision Changes Path 1.174 +38 -21 httpd-docs-2.0/htdocs/manual/mod/core.html Index: core.html =================================================================== RCS file: /home/cvs/httpd-docs-2.0/htdocs/manual/mod/core.html,v retrieving revision 1.173 retrieving revision 1.174 diff -u -r1.173 -r1.174 --- core.html 2000/10/06 00:56:48 1.173 +++ core.html 2000/10/23 22:41:58 1.174 @@ -1290,13 +1290,15 @@ This directive allows inclusion of other configuration files from within the server configuration files. +

If Include 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. +

KeepAlive directive

-Syntax: (Apache 1.1) KeepAlive max-requests
-Default: (Apache 1.1) KeepAlive 5
-Syntax: (Apache 1.2) KeepAlive on/off
-Default: (Apache 1.2) KeepAlive On
+Syntax: KeepAlive on/off
+Default: KeepAlive On
Compatibility: KeepAlive is only available in Apache 1.1 and later.

+ +

The Keep-Alive extension to HTTP/1.0 and the persistent connection +feature of HTTP/1.1 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.

+ +

In order for Keep-Alive support to be used: +

    +
  • Keep-Alive support must be enabled by setting this directive +to On.
    • +
  • The client must support Keep-Alive requests. Most current +clients do support Keep-Alive requests.
    • +
  • 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.
    • +
+ +

See also MaxKeepAliveRequests.

-This directive enables -Keep-Alive -support. - -

Apache 1.1: Set max-requests -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 0 to disable support. - -

Apache 1.2 and later: Set to "On" to enable -persistent connections, "Off" to disable. See also the MaxKeepAliveRequests directive.

+

KeepAliveTimeout directive

Compatibility: KeepAliveTimeout is only available in Apache 1.1 and later.

+ +

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 Timeout directive applies.

+ +

Setting KeepAliveTimeout 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.

+ -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 Timeout directive -applies.

<Limit> directive