Loading docs/manual/mod/core.html +25 −25 Changes for docs/manual/mod/core.html: 25 added lines, 25 removed lines. Original line number Diff line number Diff line Loading @@ -834,6 +834,31 @@ href="#timeout"><code>Timeout</code></a> directive applies. <hr> <h2><A name="limit"><Limit> directive</A></h2> <!--%plaintext <?INDEX {\tt Limit} section directive> --> <strong>Syntax:</strong> <Limit <em>method method</em> ... > ... </Limit><br> <strong>Context:</strong> any<br> <strong>Status:</strong> core<p> <Limit> and </Limit> 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 <Limit> or <A HREF="#directory"><Directory></A> may be used; the majority will be unaffected by the <Limit>. Example: <blockquote><code> <Limit GET POST><br> require valid-user<br> </Limit></code></blockquote> If an access control directive appears outside a <Limit> 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 <Limit> 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> Loading Loading @@ -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"><Limit> directive</A></h2> <!--%plaintext <?INDEX {\tt Limit} section directive> --> <strong>Syntax:</strong> <Limit <em>method method</em> ... > ... </Limit><br> <strong>Context:</strong> any<br> <strong>Status:</strong> core<p> <Limit> and </Limit> 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 <Limit> or <A HREF="#directory"><Directory></A> may be used; the majority will be unaffected by the <Limit>. Example: <blockquote><code> <Limit GET POST><br> require valid-user<br> </Limit></code></blockquote> If an access control directive appears outside a <Limit> 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 <Limit> directive at all.</STRONG> <p><hr> <h2><a name="location"><Location> directive</a></h2> <strong>Syntax:</strong> <Location <em>URL</em>> Loading Loading
docs/manual/mod/core.html +25 −25 Changes for docs/manual/mod/core.html: 25 added lines, 25 removed lines. Original line number Diff line number Diff line Loading @@ -834,6 +834,31 @@ href="#timeout"><code>Timeout</code></a> directive applies. <hr> <h2><A name="limit"><Limit> directive</A></h2> <!--%plaintext <?INDEX {\tt Limit} section directive> --> <strong>Syntax:</strong> <Limit <em>method method</em> ... > ... </Limit><br> <strong>Context:</strong> any<br> <strong>Status:</strong> core<p> <Limit> and </Limit> 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 <Limit> or <A HREF="#directory"><Directory></A> may be used; the majority will be unaffected by the <Limit>. Example: <blockquote><code> <Limit GET POST><br> require valid-user<br> </Limit></code></blockquote> If an access control directive appears outside a <Limit> 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 <Limit> 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> Loading Loading @@ -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"><Limit> directive</A></h2> <!--%plaintext <?INDEX {\tt Limit} section directive> --> <strong>Syntax:</strong> <Limit <em>method method</em> ... > ... </Limit><br> <strong>Context:</strong> any<br> <strong>Status:</strong> core<p> <Limit> and </Limit> 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 <Limit> or <A HREF="#directory"><Directory></A> may be used; the majority will be unaffected by the <Limit>. Example: <blockquote><code> <Limit GET POST><br> require valid-user<br> </Limit></code></blockquote> If an access control directive appears outside a <Limit> 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 <Limit> directive at all.</STRONG> <p><hr> <h2><a name="location"><Location> directive</a></h2> <strong>Syntax:</strong> <Location <em>URL</em>> Loading