- <p>When multiple <directive>Require</directive> directives are
- used in a single
- <a href="../sections.html#mergin">configuration section</a>,
- the first one to authorize a user authorizes the entire request,
- and subsequent <directive>Require</directive> directives are
- ignored. In other words, all <directive>Require</directive> directives
- are enclosed in an implied <directive module="mod_authz_core"
- type="section">MatchAny</directive> directive.</p>
-
- <note><directive>Require</directive> directives may not be combined
- with the <directive module="mod_authz_core">Match</directive> directive
- or any authorization container directives, such as
- <directive module="mod_authz_core"
- type="section">MatchAll</directive>.</note>
-</usage>
-
-<seealso><a href="../howto/auth.html">Authentication, Authorization,
- and Access Control</a></seealso>
-<seealso><module>mod_authn_core</module></seealso>
-<seealso><module>mod_authz_host</module></seealso>
-</directivesynopsis>
-
-<directivesynopsis>
-<name>Match</name>
-<description>Tests whether an authenticated user is authorized by
-an authorization provider.</description>
-<syntax>Match [not] <var>entity-name</var>
-[<var>entity-name</var>] ...</syntax>
-<contextlist><context>directory</context><context>.htaccess</context>
-</contextlist>
-<override>AuthConfig</override>
-
-<usage>
- <p>This directive is similar to the
- <directive module="mod_authz_core">Require</directive> directive;
- it tests whether an authenticated user is authorized according to
- a particular authorization provider and the specified restrictions.</p>
-
- <p>Unlike the <directive module="mod_authz_core">Require</directive>
- directive, it may be used with and inside authorization container
- directives such as
- <directive module="mod_authz_core" type="section">MatchAll</directive>.</p>
-
- <p>Furthermore, its result may be negated through the use of the
- <code>not</code> option. As with other negated authorization directives,
- in this case the <directive>Match</directive> directive may only
- either fail or return a neutral result, and can therefore never
+ <p>The result of the <directive>Require</directive> directive
+ may be negated through the use of the
+ <code>not</code> option. As with the other negated authorization
+ directive <directive type="section">RequireNone</directive>,
+ when the <directive>Require</directive> directive is negated it can
+ only fail or return a neutral result, and therefore may never