PR#44758: document LimitRequestBody vs. proxy

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1031564 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en
index aa06a9fbf0051461a97c939c13b576d024e8dbdb..785b8b6479381305c577bed9b976771d96b8ab5f 100644 (file)
--- a/docs/manual/mod/core.html.en
+++ b/docs/manual/mod/core.html.en
@@ -129,6 +129,12 @@ On Windows from Apache httpd 2.3.3 and later.</td></tr>
        send data first, such as <code>ftp:</code> or <code>nntp</code>:</p>
     <div class="example"><p><code>AcceptFilter nntp none</code></p></div>
 
+    <p>The default protocol names are <code>https</code> for port 443
+       and <code>http</code> for all other ports.  To specify another protocol
+       is being used with a listening port, add the <var>protocol</var>
+       argument to the <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>
+       directive.</p>
+
     <p>The default values on FreeBSD are:</p>
     <div class="example"><p><code>
         AcceptFilter http httpready <br />
@@ -2026,7 +2032,8 @@ from the client</td></tr>
 </table>
     <p>This directive specifies the number of <var>bytes</var> from 0
     (meaning unlimited) to 2147483647 (2GB) that are allowed in a
-    request body.</p>
+    request body. See the note below for the limited applicability
+    to proxy requests.</p>
 
     <p>The <code class="directive">LimitRequestBody</code> directive allows
     the user to set a limit on the allowed size of an HTTP request
@@ -2053,6 +2060,10 @@ from the client</td></tr>
     <div class="example"><p><code>
       LimitRequestBody 102400
     </code></p></div>
+    
+    <div class="note"><p>For a full description of how this directive is interpreted by 
+    proxy requests, see the <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> documentation.</p>
+    </div>
 
 
 </div>

diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index 282f2e29a15ec1e666abf4762d1a79a48016ddb3..44d9f3dee47eb2ed590d12739cb7490ac7dd7e82 100644 (file)
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -2024,7 +2024,8 @@ from the client</description>
 <usage>
     <p>This directive specifies the number of <var>bytes</var> from 0
     (meaning unlimited) to 2147483647 (2GB) that are allowed in a
-    request body.</p>
+    request body. See the note below for the limited applicability
+    to proxy requests.</p>
 
     <p>The <directive>LimitRequestBody</directive> directive allows
     the user to set a limit on the allowed size of an HTTP request
@@ -2051,6 +2052,10 @@ from the client</description>
     <example>
       LimitRequestBody 102400
     </example>
+    
+    <note><p>For a full description of how this directive is interpreted by 
+    proxy requests, see the <module>mod_proxy</module> documentation.</p>
+    </note>
 
 </usage>
 </directivesynopsis>

diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en
index 014a9807ab53d52e30702cb893bbb2212d60caa1..cf5d94009f21a6800a4a0b6b23188cdec67dbd8f 100644 (file)
--- a/docs/manual/mod/mod_proxy.html.en
+++ b/docs/manual/mod/mod_proxy.html.en
@@ -396,6 +396,18 @@
     <code>proxy-sendchunked</code> minimizes resource usage by using
     chunked encoding.</p>
 
+    <p>Under some circumstances, the server must spool request bodies
+    to disk to satisfy the requested handling of request bodies.  For 
+    example, this spooling will occur if the original body was sent with
+    chunked encoding (and and is large), but the administrator has
+    asked for backend requests to be sent with Content-Length or as HTTP/1.0.
+    This spooling can also occur if the request body already has a
+    Content-Length header, but the server is configured to filter incoming
+    request bodies.</p>
+
+    <p><code class="directive"><a href="../mod/core.html#limitrequestbody">LimitRequestBody</a></code> only applies to
+    request bodies that the server will spool to disk</p>
+
     </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section">
 <h2><a name="x-headers" id="x-headers">Reverse Proxy Request Headers</a></h2>

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 96f3f44ea936b8aa89fb4eb66b10c78cc2606505..ba569933ff816c35a070dd08cb79202e06d8d4fa 100644 (file)
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -366,6 +366,18 @@
     <code>proxy-sendchunked</code> minimizes resource usage by using
     chunked encoding.</p>
 
+    <p>Under some circumstances, the server must spool request bodies
+    to disk to satisfy the requested handling of request bodies.  For 
+    example, this spooling will occur if the original body was sent with
+    chunked encoding (and and is large), but the administrator has
+    asked for backend requests to be sent with Content-Length or as HTTP/1.0.
+    This spooling can also occur if the request body already has a
+    Content-Length header, but the server is configured to filter incoming
+    request bodies.</p>
+
+    <p><directive module="core">LimitRequestBody</directive> only applies to
+    request bodies that the server will spool to disk</p>
+
     </section> <!-- /request-bodies -->
 
     <section id="x-headers"><title>Reverse Proxy Request Headers</title>