From: pcs
+
+<Limit> and </Limit> are used to enclose a group of
+access control directives which will then apply only to the specified
+access methods, where method is any valid HTTP method.
+Any directive except another <Limit> or
+<Directory> may be used; the majority will be
+unaffected by the <Limit>. Example:
+Timeout
directive
applies.
+<Limit> directive
+
+Syntax:
+ <Limit method method ... > ... </Limit>
+Context: any
+Status: core
+
+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.
+If you wish to limit all methods, do not include any
+<Limit> directive at all.
+<Limit GET POST>
+require valid-user
+</Limit>
+
Listen directive
Syntax:
Listen [IP address:]port number
@@ -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 listen(2)
system call.
- -<Limit> and </Limit> are used to enclose a group of -access control directives which will then apply only to the specified -access methods, where method is any valid HTTP method. -Any directive except another <Limit> or -<Directory> may be used; the majority will be -unaffected by the <Limit>. Example: -
-<Limit GET POST>
-require valid-user
-</Limit>
-
-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.
-If you wish to limit all methods, do not include any
-<Limit> directive at all.