httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@locus.apache.org
Subject cvs commit: httpd-docs-2.0/htdocs/manual/mod mod_log_config.html
Date Mon, 13 Nov 2000 02:03:37 GMT
slive       00/11/12 18:03:37

  Modified:    htdocs/manual/misc FAQ-B.html FAQ-D.html
               htdocs/manual dns-caveats.html
               htdocs/manual/mod mod_log_config.html
  Log:
  Fix a few broken links.
  
  Revision  Changes    Path
  1.5       +10 -11    httpd-docs-2.0/htdocs/manual/misc/FAQ-B.html
  
  Index: FAQ-B.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-2.0/htdocs/manual/misc/FAQ-B.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -d -b -u -r1.4 -r1.5
  --- FAQ-B.html	2000/11/01 19:18:03	1.4
  +++ FAQ-B.html	2000/11/13 02:03:36	1.5
  @@ -31,7 +31,7 @@
     <!--#include virtual="header.html" -->
     <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
     <P>
  -  $Revision: 1.4 $ ($Date: 2000/11/01 19:18:03 $)
  +  $Revision: 1.5 $ ($Date: 2000/11/13 02:03:36 $)
     </P>
     <P>
     The latest version of this FAQ is always available from the main
  @@ -129,7 +129,7 @@
       </P>
      </LI>
      <LI><STRONG>Check the
  -    <A HREF="http://www.apache.org/docs/misc/FAQ.html">FAQ</A>!</STRONG>
  +    <A HREF="http://httpd.apache.org/docs/misc/FAQ.html">FAQ</A>!</STRONG>
       <P>
       The latest version of the Apache Frequently-Asked Questions list can
       always be found at the main Apache web site.
  @@ -171,7 +171,7 @@
       If you've gone through those steps above that are appropriate and
       have obtained no relief, then please <EM>do</EM> let The Apache
       Group know about the problem by
  -    <A HREF="http://www.apache.org/bug_report.html">logging a bug report</A>.
  +    <A HREF="http://httpd.apache.org/bug_report.html">logging a bug report</A>.
       </P>
       <P>
       If your problem involves the server crashing and generating a core
  @@ -261,8 +261,8 @@
     that may be able to stand behind the software and provide you with
     any assurances you may require.  You may find links to some of these
     vendors at
  -  <samp>&lt;<a href="http://www.apache.org/info/support.cgi"
  -            >http://www.apache.org/info/support.cgi</a>&gt;</samp>.
  +  <samp>&lt;<a href="http://httpd.apache.org/info/support.cgi"
  +            >http://httpd.apache.org/info/support.cgi</a>&gt;</samp>.
     </p>
     <p>
     The Apache HTTP server software is distributed with the following
  @@ -291,7 +291,7 @@
      The Apache Group encourages patches from outside developers. There
      are 2 main "types" of patches: small bugfixes and general
      improvements. Bugfixes should be submitting using the Apache <A
  -   HREF="http://www.apache.org/bug_report.html">bug report page</A>.
  +   HREF="http://httpd.apache.org/bug_report.html">bug report page</A>.
      Improvements, modifications, and additions should follow the
      instructions below.
      </P>
  @@ -370,8 +370,7 @@
        </A>
     <P>
     Check out Dean Gaudet's
  -  <A HREF="http://www.apache.org/docs/misc/perf-tuning.html"
  -  >performance tuning page</A>.
  +  <A HREF="perf-tuning.html">performance tuning page</A>.
     </P>
     <HR>
    </LI>
  @@ -392,7 +391,7 @@
      We implement a simple subset of Perl's regex support, but it's
      still a good way to learn what they mean.  You can start by going
      to the <A
  -   HREF="http://www.perl.com/CPAN-local/doc/manual/html/pod/perlre.html#Version_8_Regular_Expresions"
  +   HREF="http://www.perl.com/CPAN-local/doc/manual/html/pod/perlre.html#Regular_Expressions"
      >CPAN page on regular expressions</A>, and branching out from
      there.
      </P>
  @@ -414,8 +413,8 @@
      <p>
      If you don't see a kit for your platform listed in the
      binary distribution area
  -   (&lt;URL:<a href="http://www.apache.org/dist/binaries/"
  -            >http://www.apache.org/dist/binaries/</a>&gt;),
  +   (&lt;URL:<a href="http://httpd.apache.org/dist/binaries/"
  +            >http://httpd.apache.org/dist/binaries/</a>&gt;),
      it means either that the platform isn't available to any of
      the developers, or that they just haven't gotten around to
      preparing a binary for it.  As this is a voluntary project,
  
  
  
  1.7       +3 -3      httpd-docs-2.0/htdocs/manual/misc/FAQ-D.html
  
  Index: FAQ-D.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-2.0/htdocs/manual/misc/FAQ-D.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -d -b -u -r1.6 -r1.7
  --- FAQ-D.html	2000/07/29 19:43:35	1.6
  +++ FAQ-D.html	2000/11/13 02:03:36	1.7
  @@ -31,7 +31,7 @@
     <!--#include virtual="header.html" -->
     <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
     <P>
  -  $Revision: 1.6 $ ($Date: 2000/07/29 19:43:35 $)
  +  $Revision: 1.7 $ ($Date: 2000/11/13 02:03:36 $)
     </P>
     <P>
     The latest version of this FAQ is always available from the main
  @@ -216,9 +216,9 @@
     to rebuild the kernel with that support enabled (it's under the
     &quot;General Setup&quot; submenu).  Documentation for kernel
     building is beyond the scope of this FAQ; you should consult the <A
  -  HREF="http://www.linuxhq.com/HOWTO/Kernel-HOWTO.html" >Kernel
  +  HREF="http://www.redhat.com/mirrors/LDP/HOWTO/Kernel-HOWTO.html">Kernel
     HOWTO</A>, or the documentation provided with your distribution, or
  -  a <A HREF="http://www.linuxhq.com/HOWTO/META-FAQ.html" >Linux
  +  a <A HREF="http://www.redhat.com/mirrors/LDP/HOWTO/META-FAQ.html">Linux
     newsgroup/mailing list</A>.  As a last-resort workaround, you can
     comment out the <CODE>#define&nbsp;USE_SHMGET_SCOREBOARD</CODE>
     definition in the <SAMP>LINUX</SAMP> section of
  
  
  
  1.11      +2 -3      httpd-docs-2.0/htdocs/manual/dns-caveats.html
  
  Index: dns-caveats.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-2.0/htdocs/manual/dns-caveats.html,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -d -b -u -r1.10 -r1.11
  --- dns-caveats.html	1998/05/20 14:22:28	1.10
  +++ dns-caveats.html	2000/11/13 02:03:37	1.11
  @@ -158,9 +158,8 @@
   1.2 we've attempted to make the server at least continue booting
   in the event of failed DNS, but it might not be the best we
   can do.  In any event requiring the use of explicit IP addresses in
  -configuration files is highly undesirable in today's Internet where <A
  -HREF="http://www.ietf.org/html.charters/pier-charter.html">renumbering
  -</A> is a necessity.
  +configuration files is highly undesirable in today's Internet where
  +renumbering is a necessity.
   
   <P>A possible work around to the theft of service attack described above
   would be to perform a reverse DNS lookup on the ip address returned by
  
  
  
  1.40      +2 -2      httpd-docs-2.0/htdocs/manual/mod/mod_log_config.html
  
  Index: mod_log_config.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-2.0/htdocs/manual/mod/mod_log_config.html,v
  retrieving revision 1.39
  retrieving revision 1.40
  diff -u -d -b -u -r1.39 -r1.40
  --- mod_log_config.html	2000/11/03 01:36:51	1.39
  +++ mod_log_config.html	2000/11/13 02:03:37	1.40
  @@ -35,7 +35,7 @@
   ><STRONG>Module Identifier:</STRONG></A> config_log_module
   <BR>
   <A
  -HREF="module-dict.html#compatibility"
  +HREF="module-dict.html#Compatibility"
   REL="Help"
   ><STRONG>Compatibility:</STRONG></A> Was an extension module prior
to Apache 1.2.
   </P>
  @@ -241,7 +241,7 @@
   
   <H2>Security Considerations</H2>
   
  -See the <A HREF="../misc/security_tips.html#security">security tips</A>
  +See the <A HREF="../misc/security_tips.html#serverroot">security tips</A>
   document for details on why your security could be compromised if the
   directory where logfiles are stored is writable by anyone other than
   the user that starts the server.
  
  
  

Mime
View raw message