httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Covener <cove...@gmail.com>
Subject Fwd: svn commit: r1031564 - in /httpd/httpd/trunk/docs/manual/mod: core.html.en core.xml mod_proxy.html.en mod_proxy.xml
Date Fri, 05 Nov 2010 14:01:27 GMT
can someone review that this makes sense w/out necessarily validating
the spooling details?

---------- Forwarded message ----------
From:  <covener@apache.org>
Date: Fri, Nov 5, 2010 at 9:55 AM
Subject: svn commit: r1031564 - in /httpd/httpd/trunk/docs/manual/mod:
core.html.en core.xml mod_proxy.html.en mod_proxy.xml
To: cvs@httpd.apache.org


Author: covener
Date: Fri Nov  5 13:55:38 2010
New Revision: 1031564

URL: http://svn.apache.org/viewvc?rev=1031564&view=rev
Log:
PR#44758: document LimitRequestBody vs. proxy

Modified:
   httpd/httpd/trunk/docs/manual/mod/core.html.en
   httpd/httpd/trunk/docs/manual/mod/core.xml
   httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
   httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml

Modified: httpd/httpd/trunk/docs/manual/mod/core.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.html.en?rev=1031564&r1=1031563&r2=1031564&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.html.en Fri Nov  5 13:55:38 2010
@@ -129,6 +129,12 @@ On Windows from Apache httpd 2.3.3 and l
       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>

Modified: httpd/httpd/trunk/docs/manual/mod/core.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.xml?rev=1031564&r1=1031563&r2=1031564&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.xml Fri Nov  5 13:55:38 2010
@@ -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>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en?rev=1031564&r1=1031563&r2=1031564&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en Fri Nov  5 13:55:38 2010
@@ -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>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml?rev=1031564&r1=1031563&r2=1031564&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml Fri Nov  5 13:55:38 2010
@@ -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

-- 
Eric Covener
covener@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Mime
View raw message