From: Marc Slemko Date: Thu, 6 Feb 1997 05:28:58 +0000 (+0000) Subject: Fix docs typos. X-Git-Tag: APACHE_1_2b7~11 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=903f59697c2b247ce2d9e416ff592391bf17cb9c;p=apache Fix docs typos. Submitted by: Rodent of Unusual Size Reviewed by: Marc Slemko git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77566 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_auth.html b/docs/manual/mod/mod_auth.html index ac44fd6103..6d40ade4cd 100644 --- a/docs/manual/mod/mod_auth.html +++ b/docs/manual/mod/mod_auth.html @@ -85,7 +85,7 @@ See also AuthName, Setting the AuthAuthoritative directive explicitly to 'off' allows for both authentification and authorization to be passed on to lower level modules (as defined in the Configuration and -modules.c file if there is no userID or +modules.c files) if there is no userID or rule matching the supplied userID. If there is a userID and/or rule specified; the usual password and access checks will be applied and a failure will give an Authorization Required reply. diff --git a/docs/manual/mod/mod_auth_db.html b/docs/manual/mod/mod_auth_db.html index c2566c1785..6bd64171e7 100644 --- a/docs/manual/mod/mod_auth_db.html +++ b/docs/manual/mod/mod_auth_db.html @@ -118,7 +118,7 @@ Setting the AuthDBAuthoritative directive explicitly to 'off' allows for So if a userID appears in the database of more than one module; or if a valid require directive applies to more than one module; then the first module will verify the credentials; and no access is passed on; regardless of the AuthAuthoritative setting.

A common use for this is in conjection with one of the basic auth modules; such -as mod_auth.c. Whereas this DB module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file. +as mod_auth.c. Whereas this DB module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file.

Default: By default; control is not passed on; and an unkown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour.

diff --git a/docs/manual/mod/mod_auth_dbm.html b/docs/manual/mod/mod_auth_dbm.html index 201df5e7d2..486c0c1522 100644 --- a/docs/manual/mod/mod_auth_dbm.html +++ b/docs/manual/mod/mod_auth_dbm.html @@ -119,7 +119,7 @@ Setting the AuthDBMAuthoritative directive explicitly to 'off' allows for So if a userID appears in the database of more than one module; or if a valid require directive applies to more than one module; then the first module will verify the credentials; and no access is passed on; regardless of the AuthAuthoritative setting.

A common use for this is in conjection with one of the basic auth modules; such -as mod_auth.c. Whereas this DBM module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file. +as mod_auth.c. Whereas this DBM module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file.

Default: By default; control is not passed on; and an unkown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour.