marc        97/07/05 10:31:00

  Modified:    htdocs/manual/misc  Tag: APACHE_1_2_X  FAQ.html
  Log:
  Fix typos.
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.63.2.8  +3 -3      apache/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.63.2.7
  retrieving revision 1.63.2.8
  diff -C3 -r1.63.2.7 -r1.63.2.8
  *** FAQ.html  1997/07/05 15:49:38     1.63.2.7
  --- FAQ.html  1997/07/05 17:30:58     1.63.2.8
  ***************
  *** 15,21 ****
      <!--#include virtual="header.html" -->
      <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
      <P>
  !   $Revision: 1.63.2.7 $ ($Date: 1997/07/05 15:49:38 $)
      </P>
      <P>
      The latest version of this FAQ is always available from the main
  --- 15,21 ----
      <!--#include virtual="header.html" -->
      <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
      <P>
  !   $Revision: 1.63.2.8 $ ($Date: 1997/07/05 17:30:58 $)
      </P>
      <P>
      The latest version of this FAQ is always available from the main
  ***************
  *** 1703,1710 ****
      </P>
      <P>
      A typical situation for this error is when you are using the
  !   <SAMP>mod_auth_dbm</SAMP, <SAMP>mod_auth_msql</SAMP>,
  !   <SAMP<mod_auth_mysql</SAMP>, <SAMP>mod_auth_anon</SAMP> or
      <SAMP>mod_auth_cookie</SAMP> modules on their own.  These are by
      default <STRONG>not</STRONG> authoritative, and this will pass the
      buck on to the (non-existent) next authentification module when the
  --- 1703,1710 ----
      </P>
      <P>
      A typical situation for this error is when you are using the
  !   <SAMP>mod_auth_dbm</SAMP>, <SAMP>mod_auth_msql</SAMP>,
  !   <SAMP>mod_auth_mysql</SAMP>, <SAMP>mod_auth_anon</SAMP> or
      <SAMP>mod_auth_cookie</SAMP> modules on their own.  These are by
      default <STRONG>not</STRONG> authoritative, and this will pass the
      buck on to the (non-existent) next authentification module when the
  
  
  

Reply via email to