httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <m...@hyperreal.com>
Subject cvs commit: apache/htdocs/manual/mod mod_auth.html mod_auth_db.html mod_auth_dbm.html
Date Thu, 06 Feb 1997 05:29:00 GMT
marc        97/02/05 21:28:59

  Modified:    htdocs/manual/mod  mod_auth.html mod_auth_db.html
                        mod_auth_dbm.html
  Log:
  Fix docs typos.
  
  Submitted by: Rodent of Unusual Size <coar@decus.org>
  Reviewed by: Marc Slemko
  
  Revision  Changes    Path
  1.6       +1 -1      apache/htdocs/manual/mod/mod_auth.html
  
  Index: mod_auth.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_auth.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -C3 -r1.5 -r1.6
  *** mod_auth.html	1997/01/22 03:51:32	1.5
  --- mod_auth.html	1997/02/06 05:28:57	1.6
  ***************
  *** 85,91 ****
    Setting the AuthAuthoritative directive explicitly to <b>'off'</b>
    allows for both authentification and authorization to be passed on to
    lower level modules (as defined in the <code>Configuration</code> and
  ! <code>modules.c</code> file if there is <b>no userID</b> or
    <b>rule</b> 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.
  --- 85,91 ----
    Setting the AuthAuthoritative directive explicitly to <b>'off'</b>
    allows for both authentification and authorization to be passed on to
    lower level modules (as defined in the <code>Configuration</code> and
  ! <code>modules.c</code> files) if there is <b>no userID</b> or
    <b>rule</b> 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.
  
  
  
  1.6       +1 -1      apache/htdocs/manual/mod/mod_auth_db.html
  
  Index: mod_auth_db.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_auth_db.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -C3 -r1.5 -r1.6
  *** mod_auth_db.html	1996/12/24 19:08:23	1.5
  --- mod_auth_db.html	1997/02/06 05:28:57	1.6
  ***************
  *** 118,124 ****
    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.
    <p>
    A common use for this is in conjection with one of the basic auth modules; such
  ! as <a href="mod_auth.c"><code>mod_auth.c</code></a>. 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.
    <p>
    <b>Default:</b> 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.
    <p>
  --- 118,124 ----
    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.
    <p>
    A common use for this is in conjection with one of the basic auth modules; such
  ! as <a href="mod_auth.html"><code>mod_auth.c</code></a>. 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.
    <p>
    <b>Default:</b> 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.
    <p>
  
  
  
  1.7       +1 -1      apache/htdocs/manual/mod/mod_auth_dbm.html
  
  Index: mod_auth_dbm.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_auth_dbm.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -C3 -r1.6 -r1.7
  *** mod_auth_dbm.html	1996/12/24 19:08:24	1.6
  --- mod_auth_dbm.html	1997/02/06 05:28:58	1.7
  ***************
  *** 119,125 ****
    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.
    <p>
    A common use for this is in conjection with one of the basic auth modules; such
  ! as <a href="mod_auth.c"><code>mod_auth.c</code></a>. 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.
    <p>
    <b>Default:</b> 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.
    <p>
  --- 119,125 ----
    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.
    <p>
    A common use for this is in conjection with one of the basic auth modules; such
  ! as <a href="mod_auth.html"><code>mod_auth.c</code></a>. 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.
    <p>
    <b>Default:</b> 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.
    <p>
  
  
  

Mime
View raw message