Commit 33354b85 authored by pcs's avatar pcs
Browse files

Put <Limit> into its correct alphabetical position.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@79362 13f79535-47bb-0310-9956-ffa450edef68
parent 4d502582
Loading
Loading
Loading
Loading
+25 −25
Changes for docs/manual/mod/core.html: 25 added lines, 25 removed lines.
Original line number Diff line number Diff line
@@ -834,6 +834,31 @@ href="#timeout"><code>Timeout</code></a> directive
applies.
<hr>

<h2><A name="limit">&lt;Limit&gt; directive</A></h2>
<!--%plaintext &lt;?INDEX {\tt Limit} section directive&gt; -->
<strong>Syntax:</strong>
 &lt;Limit <em>method method</em> ... &gt; ... &lt;/Limit&gt;<br>
<strong>Context:</strong> any<br>
<strong>Status:</strong> core<p>

&lt;Limit&gt; and &lt;/Limit&gt; are used to enclose a group of
access control directives which will then apply only to the specified
access methods, where <em>method</em> is any valid HTTP method.
Any directive except another &lt;Limit&gt; or
<A HREF="#directory">&lt;Directory&gt;</A> may be used; the majority will be
unaffected by the &lt;Limit&gt;. Example:
<blockquote><code>
&lt;Limit GET POST&gt;<br>
require valid-user<br>
&lt;/Limit&gt;</code></blockquote>

If an access control directive appears outside a &lt;Limit&gt;
directive, then it applies to all access methods. The method names
listed can be one or more of: GET, POST, PUT, DELETE, CONNECT or
OPTIONS. If GET is used it will also restrict HEAD requests.
<STRONG>If you wish to limit all methods, do not include any
&lt;Limit&gt; directive at all.</STRONG> <p><hr>

<h2><A name="listen">Listen directive</A></h2>
<strong>Syntax:</strong>
Listen [<em>IP address</em>:]<em>port number</em><br>
@@ -901,31 +926,6 @@ tuning is needed or desired, however on some systems it is desirable
to increase this when under a TCP SYN flood attack.  See
the backlog parameter to the <code>listen(2)</code> system call.</p><hr>

<h2><A name="limit">&lt;Limit&gt; directive</A></h2>
<!--%plaintext &lt;?INDEX {\tt Limit} section directive&gt; -->
<strong>Syntax:</strong>
 &lt;Limit <em>method method</em> ... &gt; ... &lt;/Limit&gt;<br>
<strong>Context:</strong> any<br>
<strong>Status:</strong> core<p>

&lt;Limit&gt; and &lt;/Limit&gt; are used to enclose a group of
access control directives which will then apply only to the specified
access methods, where <em>method</em> is any valid HTTP method.
Any directive except another &lt;Limit&gt; or
<A HREF="#directory">&lt;Directory&gt;</A> may be used; the majority will be
unaffected by the &lt;Limit&gt;. Example:
<blockquote><code>
&lt;Limit GET POST&gt;<br>
require valid-user<br>
&lt;/Limit&gt;</code></blockquote>

If an access control directive appears outside a &lt;Limit&gt;
directive, then it applies to all access methods. The method names
listed can be one or more of: GET, POST, PUT, DELETE, CONNECT or
OPTIONS. If GET is used it will also restrict HEAD requests.
<STRONG>If you wish to limit all methods, do not include any
&lt;Limit&gt; directive at all.</STRONG> <p><hr>

<h2><a name="location">&lt;Location&gt; directive</a></h2>

<strong>Syntax:</strong> &lt;Location <em>URL</em>&gt;