httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod core.xml
Date Wed, 02 Jul 2003 01:16:33 GMT
nd          2003/07/01 18:16:33

  Modified:    docs/manual/mod Tag: APACHE_2_0_BRANCH core.xml
  Log:
  backport LimitInternalRecursion documentation
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.46.2.24 +35 -0     httpd-2.0/docs/manual/mod/core.xml
  
  Index: core.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.xml,v
  retrieving revision 1.46.2.23
  retrieving revision 1.46.2.24
  diff -u -r1.46.2.23 -r1.46.2.24
  --- core.xml	30 Jun 2003 19:25:26 -0000	1.46.2.23
  +++ core.xml	2 Jul 2003 01:16:31 -0000	1.46.2.24
  @@ -1517,6 +1517,41 @@
   </directivesynopsis>
   
   <directivesynopsis>
  +<name>LimitInternalRecursion</name>
  +<description>Determine maximum number of internal redirects and nested
  +subrequests</description>
  +<syntax>LimitInternalRecursion <var>number</var> [<var>number</var>]</syntax>
  +<default>LimitInternalRecursion 10</default>
  +<contextlist><context>server config</context><context>virtual host</context>
  +</contextlist>
  +<compatibility>Available in Apache 2.0.47 and later</compatibility>
  +
  +<usage>
  +    <p>An internal redirect happens, for example, when using the <directive
  +    module="mod_actions">Action</directive> directive, which internally
  +    redirects the original request to a CGI script. A subrequest is Apache's
  +    mechanism to find out what would happen for some URI if it were requested.
  +    For example, <module>mod_dir</module> uses subrequests to look for the
  +    files listed in the <directive module="mod_dir">DirectoryIndex</directive>
  +    directive.</p>
  +
  +    <p><directive>LimitInternalRecursion</directive> prevents the server
  +    from crashing when entering an infinite loop of internal redirects or
  +    subrequests. Such loops are usually caused by misconfigurations.</p>
  +
  +    <p>The directive stores two different limits, which are evaluated on
  +    per-request basis. The first <var>number</var> is the maximum number of
  +    internal redirects, that may follow each other. The second <var>number</var>
  +    determines, how deep subrequests may be nested. If you specify only one
  +    <var>number</var>, it will be assigned to both limits.</p>
  +
  +    <example><title>Example</title>
  +      LimitInternalRecursion 5
  +    </example>
  +</usage>
  +</directivesynopsis>
  +
  +<directivesynopsis>
   <name>LimitRequestBody</name>
   <description>Restricts the total size of the HTTP request body sent
   from the client</description>
  
  
  

Mime
View raw message