Commit 21d3e1d8 authored by Ken Coar's avatar Ken Coar
Browse files 

	The semi-regular HTML cleanup of the documentation.  There are
	some HTML errors (incorrect anchor nesting, primarily) coming in
	another commit.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@82064 13f79535-47bb-0310-9956-ffa450edef68
parent d88afdf9

docs/manual/content-negotiation.html

+5 −5
Original line number Diff line number Diff line
@@ -422,9 +422,9 @@ different naming conventions, because files can have more than one 
extension, and the order of the extensions is normally irrelevant

(see <A HREF="mod/mod_mime.html">mod_mime</A> documentation for details).

<P>

A typical file has a MIME-type extension (e.g. <SAMP>html</SAMP>),

maybe an encoding extension (e.g. <SAMP>gz</SAMP> and of course a

language extension (e.g. <SAMP>en</SAMP>) when we have different

A typical file has a MIME-type extension (<EM>e.g.</EM>, <SAMP>html</SAMP>),

maybe an encoding extension (<EM>e.g.</EM>, <SAMP>gz</SAMP>), and of course a

language extension (<EM>e.g.</EM>, <SAMP>en</SAMP>) when we have different

language variants of this file.



<P>
@@ -489,7 +489,7 @@ hyperlinks: 


<P>

Looking at the table above you will notice that it is always possible to

use the name without any extensions  in an hyperlink (e.g. <SAMP>foo</SAMP>).

use the name without any extensions  in an hyperlink (<EM>e.g.</EM>, <SAMP>foo</SAMP>).

The advantage is that you can hide the actual type of a

document rsp. file and can change it later, e.g. from <SAMP>html</SAMP>

to <SAMP>shtml</SAMP> or <SAMP>cgi</SAMP> without changing any
@@ -499,7 +499,7 @@ hyperlink references. 
If you want to continue to use a MIME-type in your hyperlinks (e.g.

<SAMP>foo.html</SAMP>) the language extension (including an encoding extension

if there is one) must be on the right hand side of the MIME-type extension

(e.g. <SAMP>foo.html.en</SAMP>).

(<EM>e.g.</EM>, <SAMP>foo.html.en</SAMP>).





<H2>Note on Caching</H2>

docs/manual/content-negotiation.html.en

+5 −5
Original line number Diff line number Diff line
@@ -422,9 +422,9 @@ different naming conventions, because files can have more than one 
extension, and the order of the extensions is normally irrelevant

(see <A HREF="mod/mod_mime.html">mod_mime</A> documentation for details).

<P>

A typical file has a MIME-type extension (e.g. <SAMP>html</SAMP>),

maybe an encoding extension (e.g. <SAMP>gz</SAMP> and of course a

language extension (e.g. <SAMP>en</SAMP>) when we have different

A typical file has a MIME-type extension (<EM>e.g.</EM>, <SAMP>html</SAMP>),

maybe an encoding extension (<EM>e.g.</EM>, <SAMP>gz</SAMP>), and of course a

language extension (<EM>e.g.</EM>, <SAMP>en</SAMP>) when we have different

language variants of this file.



<P>
@@ -489,7 +489,7 @@ hyperlinks: 


<P>

Looking at the table above you will notice that it is always possible to

use the name without any extensions  in an hyperlink (e.g. <SAMP>foo</SAMP>).

use the name without any extensions  in an hyperlink (<EM>e.g.</EM>, <SAMP>foo</SAMP>).

The advantage is that you can hide the actual type of a

document rsp. file and can change it later, e.g. from <SAMP>html</SAMP>

to <SAMP>shtml</SAMP> or <SAMP>cgi</SAMP> without changing any
@@ -499,7 +499,7 @@ hyperlink references. 
If you want to continue to use a MIME-type in your hyperlinks (e.g.

<SAMP>foo.html</SAMP>) the language extension (including an encoding extension

if there is one) must be on the right hand side of the MIME-type extension

(e.g. <SAMP>foo.html.en</SAMP>).

(<EM>e.g.</EM>, <SAMP>foo.html.en</SAMP>).





<H2>Note on Caching</H2>

docs/manual/install.html

+1 −1
Original line number Diff line number Diff line
@@ -65,7 +65,7 @@ directory of the Apache distribution. Change into this directory. 
 <LI>

  Configure Apache for your operating system. Normally you can just

  type run the <CODE>Configure</CODE> script as given below. However

  if this fails or you have any special requirements (e.g. to include

  if this fails or you have any special requirements (<EM>e.g.</EM>, to include

  an additional library required by an optional module) you might need

  to edit one or more of the following options in the

  <CODE>Configuration</CODE> file:

docs/manual/install.html.en

+1 −1
Original line number Diff line number Diff line
@@ -65,7 +65,7 @@ directory of the Apache distribution. Change into this directory. 
 <LI>

  Configure Apache for your operating system. Normally you can just

  type run the <CODE>Configure</CODE> script as given below. However

  if this fails or you have any special requirements (e.g. to include

  if this fails or you have any special requirements (<EM>e.g.</EM>, to include

  an additional library required by an optional module) you might need

  to edit one or more of the following options in the

  <CODE>Configuration</CODE> file:

docs/manual/misc/FAQ.html

+20 −20
Original line number Diff line number Diff line
@@ -14,7 +14,7 @@ 
  <!--#include virtual="header.html" -->

  <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>

  <P>

  $Revision: 1.127 $ ($Date: 1998/09/09 16:01:03 $)

  $Revision: 1.128 $ ($Date: 1998/09/17 12:33:01 $)

  </P>

  <P>

  The latest version of this FAQ is always available from the main
@@ -418,7 +418,7 @@ 
    occasional users.

   </LI>

  </UL>

  <p></P>

  <P></P>

  <HR>

 </LI>
@@ -552,7 +552,7 @@ 
      (dbx) where</CODE>

     </DD>

    </DL>

    <p></P>

    <P></P>

    <P>

    (Substitute the appropriate locations for your

    <SAMP>ServerRoot</SAMP> and your <SAMP>httpd</SAMP> and
@@ -618,7 +618,7 @@ 
     <DD><CODE>AddHandler cgi-script .cgi</CODE>

     </DD>

    </DL>

    <p></P>

    <P></P>

    <P>

    The server will then recognize that all files in that location (and

    its logical descendants) that end in &quot;<SAMP>.cgi</SAMP>&quot;
@@ -630,7 +630,7 @@ 
    declaration that includes the <SAMP>ExecCGI</SAMP> option.

   </LI>

  </OL>

  <p></P>

  <P></P>

  <P>

  In some situations, you might not want to actually

  allow all files named &quot;<SAMP>*.cgi</SAMP>&quot; to be executable.
@@ -652,7 +652,7 @@ 
      RewriteRule   ^quux\.cgi$  -  [T=application/x-httpd-cgi]</CODE>

     </DD>

    </DL>

    <p></P>

    <P></P>

   </LI>

   <LI>Make sure that the directory location is covered by an

    <A HREF="../mod/core.html#options"><SAMP>Options</SAMP></A>
@@ -660,7 +660,7 @@ 
    <SAMP>FollowSymLinks</SAMP> option.

   </LI>

  </OL>

  <p></P>

  <P></P>

  <HR>

 </LI>
@@ -703,7 +703,7 @@ 
    }</CODE>

   </DD>

  </DL>

  <p></P>

  <P></P>

  <P>

  This is generally only necessary when you are calling external

  programs from your script that send output to stdout, or if there will
@@ -764,7 +764,7 @@ 
     <DD><CODE>AddHandler server-parsed .shtml</CODE>

     </DD>

    </DL>

    <p></P>

    <P></P>

    <P>

    This indicates that all files ending in &quot;.shtml&quot; in that

    location (or its descendants) should be parsed.  Note that using
@@ -1195,7 +1195,7 @@ 
    BrowserMatch JDK/1.0 force-response-1.0</CODE>

   </DD>

  </DL>

  <p></P>

  <P></P>

  <P>

  More information about this issue can be found in the

  <A HREF="http://www.apache.org/info/jdk-102.html"
@@ -1308,7 +1308,7 @@ 
    This hurts performance and should only be used as a last resort.

   </LI>

  </UL>

  <p></P>

  <P></P>

  <HR>

 </LI>
@@ -1381,7 +1381,7 @@ 
     <DD><CODE>EXTRA_CFLAGS=-DMAXIMUM_DNS</CODE>

     </DD>

    </DL>

    <p></P>

    <P></P>

    <P>

    This will cause Apache to be very paranoid about making sure a

    particular host address is <EM>really</EM> assigned to the name it
@@ -1459,7 +1459,7 @@ 
     <DD><CODE>AddType audio/x-midi .mid .midi .kar</CODE>

     </DD>

    </DL>

    <p></P>

    <P></P>

    <P>

    Note that this may break browsers that <EM>do</EM> recognize the

    <SAMP>audio/midi</SAMP> MIME type unless they're prepared to also
@@ -1600,7 +1600,7 @@ 
    EXTRA_LIBS=-lbind</CODE>

   </DD>

  </DL>

  <p></P>

  <P></P>

  <HR>

 </LI>
@@ -1710,7 +1710,7 @@ 
    satisfy any</CODE>

   </DD>

  </DL>

  <p></P>

  <P></P>

  <P>

  See the <A HREF="#user-authentication">user authentication</A>

  question and the <A HREF="../mod/mod_access.html">mod_access</A>
@@ -2299,7 +2299,7 @@ 
    <P>

    If you fail to do this, then it is very likely that Apache will fail

    to build.  One of the most common errors is with <CODE>readv</CODE>,

    <CODE>writev</CODE>, or <CODE>uio.h</CODE>.  This is <B>not</B> a

    <CODE>writev</CODE>, or <CODE>uio.h</CODE>.  This is <STRONG>not</STRONG> a

    bug with Apache.  You will need to re-install GCC.

   <HR>

  </LI>
@@ -2324,11 +2324,11 @@ 
   Improvements, modifications and additions should follow these instructions.

   <P>

   In general, the first course of action is to be a member of the

   <code>new-httpd@apache.org</code> mailing list. This indicates to the Group that

   <CODE>new-httpd@apache.org</CODE> mailing list. This indicates to the Group that

   you are closely following the latest Apache developments. Your patch file should be

   generated using either '<code>diff -c</code>' or '<code>diff -u</code>' against the

   latest CVS tree. To submit your patch, send Email to <code>new-httpd@apache.org</code>

   with a <code>Subject:</code> line that starts with <code>[PATCH]</code> and

   generated using either '<CODE>diff -c</CODE>' or '<CODE>diff -u</CODE>' against the

   latest CVS tree. To submit your patch, send Email to <CODE>new-httpd@apache.org</CODE>

   with a <CODE>Subject:</CODE> line that starts with <CODE>[PATCH]</CODE> and

   includes a general description of the patch. In the body of the message, the

   patch should be clearly described and then included at the end of the message.

   If the patch-file is long, you can note a URL to the file instead of the file