This is an automated email from the ASF dual-hosted git repository.

markt-asf pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/9.0.x by this push:
     new d67020a926 Fix BZ 69617 - expand maxHttpRequestHeaderSize docs
d67020a926 is described below

commit d67020a9267f71ef88b95d590dbc8074282e00dd
Author: Mark Thomas <[email protected]>
AuthorDate: Mon Oct 19 12:03:02 2026 +0100

    Fix BZ 69617 - expand maxHttpRequestHeaderSize docs
---
 webapps/docs/changelog.xml   |  5 +++++
 webapps/docs/config/http.xml | 11 +++++++----
 2 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml
index 50f80544d2..6b645456a4 100644
--- a/webapps/docs/changelog.xml
+++ b/webapps/docs/changelog.xml
@@ -420,6 +420,11 @@
         Host Manager: Host names are now always converted to lower case before
         use. (markt)
       </fix>
+      <fix>
+        Documentation: Expand the documentation of the
+        <code>maxHttpRequestHeaderSize</code> attribute for the HTTP connector.
+        (markt)
+      </fix>
     </changelog>
   </subsection>
   <subsection name="Tribes">
diff --git a/webapps/docs/config/http.xml b/webapps/docs/config/http.xml
index 7346228ac8..1e14c93e96 100644
--- a/webapps/docs/config/http.xml
+++ b/webapps/docs/config/http.xml
@@ -628,9 +628,11 @@
       attribute.</p>
       <p>If you see "Request header is too large" errors you can increase this,
       but be aware that Tomcat will allocate the full amount you specify for
-      every request. For example, if you specify a maxHttpRequestHeaderSize of
-      1 MB and your application handles 100 concurrent requests, you will see
-      100 MB of heap consumed by request headers.</p>
+      every request and that those requests are not garbage collected after use
+      but are recycled and re-used (see <code>processorCache</code>). For
+      example, if you specify a maxHttpRequestHeaderSize of 1 MB and your
+      application handles 100 concurrent requests, you will see 100 MB of heap
+      consumed by request headers.</p>
     </attribute>
 
     <attribute name="maxHttpResponseHeaderSize" required="false">
@@ -726,7 +728,8 @@
     </attribute>
 
     <attribute name="processorCache" required="false">
-      <p>The protocol handler caches Processor objects to speed up performance.
+      <p>The protocol handler caches Processor objects (and related internal
+      objects such as the request and response) to speed up performance.
       This setting dictates how many of these objects get cached.
       <code>-1</code> means unlimited, default is <code>200</code>.
       <code>0</code> means no request processor reuse. This has a very


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to