httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <m...@hyperreal.org>
Subject cvs commit: apache/htdocs/manual/misc FAQ.html
Date Sat, 05 Jul 1997 17:33:36 GMT
marc        97/07/05 10:33:36

  Modified:    htdocs/manual/misc  FAQ.html
  Log:
  Fix typos.
  
  Revision  Changes    Path
  1.80      +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.79
  retrieving revision 1.80
  diff -C3 -r1.79 -r1.80
  *** FAQ.html	1997/07/05 15:46:46	1.79
  --- FAQ.html	1997/07/05 17:33:34	1.80
  ***************
  *** 15,21 ****
      <!--#include virtual="header.html" -->
      <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
      <P>
  !   $Revision: 1.79 $ ($Date: 1997/07/05 15:46:46 $)
      </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.80 $ ($Date: 1997/07/05 17:33:34 $)
      </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
  
  
  

Mime
View raw message