Mailing-List: contact apache-cvs-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Date: 8 Nov 2000 01:14:32 -0000
Message-ID: <20001108011432.79034.qmail@locus.apache.org>
From: slive@locus.apache.org
To: httpd-docs-1.3-cvs@apache.org
Subject: cvs commit: httpd-docs-1.3/htdocs/manual/mod core.html

slive       00/11/07 17:14:32

  Modified:    htdocs/manual/mod core.html
  Log:
  Make the keep-alive documentation more accurate.
  
  This could use some review from someone who understands these issues
  better than I do.
  
  Revision  Changes    Path
  1.178     +16 -14    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.177
  retrieving revision 1.178
  diff -u -r1.177 -r1.178
  --- core.html	2000/10/24 01:10:39	1.177
  +++ core.html	2000/11/08 01:14:31	1.178
  @@ -1306,21 +1306,23 @@
   1.1 and later.<P>
   
   <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>
  +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 <code>KeepAlive
  +On</code>.</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 known 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>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.</p>
   
   <P><STRONG>Apache 1.1</STRONG>: Set <EM>max-requests</EM>
   to the maximum number of requests you want Apache to entertain per