|
Lines 46-51
Link Here
|
| 46 |
<Location "/"> |
46 |
<Location "/"> |
| 47 |
AllowMethods GET POST OPTIONS |
47 |
AllowMethods GET POST OPTIONS |
| 48 |
</Location> |
48 |
</Location> |
|
|
49 |
|
| 50 |
<Location "/nopost"> |
| 51 |
AllowMethods -POST |
| 52 |
</Location> |
| 49 |
</highlight> |
53 |
</highlight> |
| 50 |
</summary> |
54 |
</summary> |
|
Lines 53-60
Link Here
|
| 53 |
<directivesynopsis> |
57 |
<directivesynopsis> |
| 54 |
<name>AllowMethods</name> |
58 |
<name>AllowMethods</name> |
| 55 |
<description>Restrict access to the listed HTTP methods</description> |
59 |
<description>Restrict access to the listed HTTP methods</description> |
| 56 |
<syntax>AllowMethods reset|<em>HTTP-method</em> |
60 |
<syntax>AllowMethods reset | [+|-]<var>HTTP-method</var> |
| 57 |
[<em>HTTP-method</em>]...</syntax> |
61 |
[ [+|-]<var>HTTP-method</var> ] ...</syntax> |
| 58 |
<default>AllowMethods reset</default> |
62 |
<default>AllowMethods reset</default> |
| 59 |
<contextlist><context>directory</context></contextlist> |
63 |
<contextlist><context>directory</context></contextlist> |
| 60 |
<status>Experimental</status> |
64 |
<status>Experimental</status> |
|
Lines 77-85
Link Here
|
| 77 |
use <directive module="core">TraceEnable</directive> instead.</p> |
81 |
use <directive module="core">TraceEnable</directive> instead.</p> |
| 78 |
</note> |
82 |
</note> |
|
|
83 |
<p>Normally, if multiple <directive>AllowMethods</directive> could |
| 84 |
apply to a directory, then the most specific one is used and |
| 85 |
others are ignored; the methods are not merged. (See <a |
| 86 |
href="../sections.html#merging">how sections are merged</a>.) |
| 87 |
However if <em>all</em> the methods on the |
| 88 |
<directive>AllowMethods</directive> directive are preceded by a |
| 89 |
<code>+</code> or <code>-</code> symbol, the options are |
| 90 |
merged. Any method preceded by a <code>+</code> are added to the |
| 91 |
methods currently in force, and any method preceded by a |
| 92 |
<code>-</code> are removed from the methods currently in |
| 93 |
force. </p> |
| 94 |
|
| 95 |
<note><title>Note</title> |
| 96 |
<p>Mixing <directive>AllowMethods</directive> with a <code>+</code> or |
| 97 |
<code>-</code> with those without is not valid syntax and will be |
| 98 |
rejected during server startup by the syntax check with an abort.</p> |
| 99 |
</note> |
| 100 |
|
| 79 |
<p><module>mod_allowmethods</module> was written to replace the rather |
101 |
<p><module>mod_allowmethods</module> was written to replace the rather |
| 80 |
kludgy implementation of <directive module="core">Limit</directive> and |
102 |
kludgy implementation of <directive module="core">Limit</directive> and |
| 81 |
<directive module="core">LimitExcept</directive>.</p> |
103 |
<directive module="core">LimitExcept</directive>.</p> |
|
|
104 |
|
| 82 |
</usage> |
105 |
</usage> |
| 83 |
</directivesynopsis> |
106 |
</directivesynopsis> |