From cb147d3b157cbeb93d46e6d7d313ef3ff5482ae5 Mon Sep 17 00:00:00 2001
From: markt <markt@13f79535-47bb-0310-9956-ffa450edef68>
Date: Wed, 4 Feb 2009 06:53:13 +0000
Subject: [PATCH] Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=46600
 Correctly document maxKeepAliveRequests

git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@740632 13f79535-47bb-0310-9956-ffa450edef68
---
 webapps/docs/config/http.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/webapps/docs/config/http.xml b/webapps/docs/config/http.xml
index ce2233b72..55ad3c8d0 100644
--- a/webapps/docs/config/http.xml
+++ b/webapps/docs/config/http.xml
@@ -513,6 +513,15 @@
            <code>-1</code> means unlimited, default is <code>200</code>. Set this value somewhere close to your maxThreads value.
         </p>
       </attribute>
+      <attribute name="maxKeepAliveRequests" required="false">
+        <p>The maximum number of HTTP requests which can be pipelined until
+        the connection is closed by the server. Setting this attribute to 1 will
+        disable HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and
+        pipelining. Setting this to -1 will allow an unlimited amount of
+        pipelined or keep-alive HTTP requests.
+        If not specified, this attribute is set to 100.</p>
+      </attribute>
+
       <attribute name="socket.directBuffer" required="false">
         <p>(bool)Boolean value, whether to use direct ByteBuffers or java mapped ByteBuffers. Default is <code>false</code>
            <br/>When you are using direct buffers, make sure you allocate the appropriate amount of memory for the 
-- 
2.11.0