From 842e9f1365c46f2be114f8bbdcbafa98bc37aebb Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Wed, 8 Nov 2000 01:15:49 +0000 Subject: [PATCH] Make the keep-alive documentation more accurate. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@86861 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index f8a8a1e6a1..740b10eedd 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -1314,21 +1314,23 @@ and parse those as configuration files. 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: -

+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 has been shown to result in an almost 50% speedup in +latency times for HTML documents with many images. To enable +Keep-Alive connections in Apache 1.2 and later, set KeepAlive +On.

+ +

For HTTP/1.0 clients, Keep-Alive connections will only be used if +they are specifically requested by a client. In addition, a +Keep-Alive connection with an HTTP/1.0 client can only be used when +the length of the content is known in advance. This implies that +dynamic content such as CGI output, SSI pages, and server-generated +directory listings will generally not use Keep-Alive connections to +HTTP/1.0 clients. For HTTP/1.1 clients, persistent connections are +the default unless otherwise specified. Chunked encoding will be used +in order to send content of unknown length over persistent +connections.

See also MaxKeepAliveRequests.

-- 2.50.1