@@ -267,15 +267,18 @@ directive.</p>
267267
268268<section id =" authzproviders" ><title >Authorization providers for use with Require</title >
269269
270- <p ><module >mod_ssl</module > provides a few authentication providers for use
271- with <module >mod_authz_core</module >'s
270+ <p ><module >mod_ssl</module > provides the following authorization providers
271+ for use with <module >mod_authz_core</module >'s
272272 <directive module =" mod_authz_core" >Require</directive > directive.</p >
273273
274274 <section id =" reqssl" ><title >Require ssl</title >
275275
276276 <p >The <code >ssl</code > provider denies access if a connection is not
277- encrypted with SSL. This is similar to the
278- <directive >SSLRequireSSL</directive > directive.</p >
277+ encrypted with SSL. Unlike the
278+ <directive >SSLRequireSSL</directive > directive, this can be
279+ combined with other <directive >Require</directive > directives in
280+ <directive module =" mod_authz_core" >RequireAny</directive > or
281+ <directive module =" mod_authz_core" >RequireAll</directive > blocks.</p >
279282
280283 <highlight language =" config" >
281284 Require ssl
@@ -285,8 +288,8 @@ directive.</p>
285288
286289 <section id =" reqverifyclient" ><title >Require ssl-verify-client</title >
287290
288- <p >The <code >ssl</code > provider allows access if the user is
289- authenticated with a valid client certificate. This is only
291+ <p >The <code >ssl-verify-client </code > provider allows access if the
292+ user is authenticated with a valid client certificate. This is only
290293 useful if <code >SSLVerifyClient optional</code > is in effect.</p >
291294
292295 <p >The following example grants access if the user is authenticated
0 commit comments