From 681969ef5dfbdecad2f0c8dc26e376bf0c0c1296 Mon Sep 17 00:00:00 2001
From: Joshua Slive If
-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 The Keep-Alive extension to HTTP/1.0 and the persistent connection
+feature of In order for Keep-Alive support to be used:
+ See also MaxKeepAliveRequests. Apache 1.2 and later: Set to "On" to enable
-persistent connections, "Off" to disable. See also the MaxKeepAliveRequests directive.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.0
to disable support.
+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.
+
+
+On
.
+
KeepAliveTimeout directive
MaxKeepAliveRequests directive.
-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.
+
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.