Commit 7e5b7d9d authored by Ken Coar's avatar Ken Coar
Browse files 

	Part 2 of the semi-regular HTML normalisation.  Now on to
	apache-site...  No thirty.


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

docs/manual/bind.html

+8 −5
Changes for docs/manual/bind.html: 8 added lines, 5 removed lines.
Original line number Diff line number Diff line
@@ -29,18 +29,21 @@ There are two directives used to restrict or specify which addresses 
and ports Apache listens to.



<UL>

<LI><A HREF="#bindaddress">BindAddress</A> is used to restrict the server to listening to

<LI><A HREF="#bindaddress">BindAddress</A> is used to restrict the server to

  listening to

  a single address, and can be used to permit multiple Apache servers

  on the same machine listening to different IP addresses.

<LI><A HREF="#listen">Listen</A> can be used to make a single Apache server listen

<LI><A HREF="#listen">Listen</A> can be used to make a single Apache server

  listen

  to more than one address and/or port.

</UL>



<H3><A name="bindaddress">BindAddress</A></H3>

<H3><A NAME="bindaddress">BindAddress</A></H3>

<A

 HREF="mod/directive-dict.html#Syntax"

 REL="Help"

><STRONG>Syntax:</STRONG></A> BindAddress <EM>[ * | IP-address | hostname ]</EM><BR>

><STRONG>Syntax:</STRONG></A> BindAddress <EM>[ * | IP-address 

 | hostname ]</EM><BR>

<A

 HREF="mod/directive-dict.html#Default"

 REL="Help"
@@ -59,7 +62,7 @@ is *, the server listens to all addresses. The port listened to 
is set with the <TT>Port</TT> directive. Only one BindAddress

should be used.



<H3><A name="listen">Listen</A></H3>

<H3><A NAME="listen">Listen</A></H3>

<A

 HREF="mod/directive-dict.html#Syntax"

 REL="Help"

docs/manual/bind.html.en

+8 −5
Changes for docs/manual/bind.html.en: 8 added lines, 5 removed lines.
Original line number Diff line number Diff line
@@ -29,18 +29,21 @@ There are two directives used to restrict or specify which addresses 
and ports Apache listens to.



<UL>

<LI><A HREF="#bindaddress">BindAddress</A> is used to restrict the server to listening to

<LI><A HREF="#bindaddress">BindAddress</A> is used to restrict the server to

  listening to

  a single address, and can be used to permit multiple Apache servers

  on the same machine listening to different IP addresses.

<LI><A HREF="#listen">Listen</A> can be used to make a single Apache server listen

<LI><A HREF="#listen">Listen</A> can be used to make a single Apache server

  listen

  to more than one address and/or port.

</UL>



<H3><A name="bindaddress">BindAddress</A></H3>

<H3><A NAME="bindaddress">BindAddress</A></H3>

<A

 HREF="mod/directive-dict.html#Syntax"

 REL="Help"

><STRONG>Syntax:</STRONG></A> BindAddress <EM>[ * | IP-address | hostname ]</EM><BR>

><STRONG>Syntax:</STRONG></A> BindAddress <EM>[ * | IP-address 

 | hostname ]</EM><BR>

<A

 HREF="mod/directive-dict.html#Default"

 REL="Help"
@@ -59,7 +62,7 @@ is *, the server listens to all addresses. The port listened to 
is set with the <TT>Port</TT> directive. Only one BindAddress

should be used.



<H3><A name="listen">Listen</A></H3>

<H3><A NAME="listen">Listen</A></H3>

<A

 HREF="mod/directive-dict.html#Syntax"

 REL="Help"

docs/manual/cgi_path.html

+4 −4
Changes for docs/manual/cgi_path.html: 4 added lines, 4 removed lines.
Original line number Diff line number Diff line
@@ -16,7 +16,7 @@ 


<HR>



<H2><A name="over">Overview</A></H2>

<H2><A NAME="over">Overview</A></H2>



<P>As implemented in Apache 1.1.1 and earlier versions, the method

Apache used to create PATH_INFO in the CGI environment was
@@ -27,7 +27,7 @@ applications, the Apache 1.2 behavior is still compatible with the 
CGI/1.1 specification, and CGI scripts can be easily modified (<A

HREF="#compat">see below</A>).



<H2><A name="prob">The Problem</A></H2>

<H2><A NAME="prob">The Problem</A></H2>



<P>Apache 1.1.1 and earlier implemented the PATH_INFO and SCRIPT_NAME

environment variables by looking at the filename, not the URL. While
@@ -46,7 +46,7 @@ SCRIPT_NAME to "<CODE>/cgi-</CODE>". Obviously, the latter is 
incorrect. In certain cases, this could even cause the server to

crash.</P>



<H2><A name="solution">The Solution</A></H2>

<H2><A NAME="solution">The Solution</A></H2>



<P>Apache 1.2 and later now determine SCRIPT_NAME and PATH_INFO by

looking directly at the URL, and determining how much of the URL is
@@ -67,7 +67,7 @@ sort of information is not a recommended method, and a script making 
use of it "deserves" not to work. Apache 1.2b3 and later, however, do

provide <A HREF="#compat">a workaround.</A>



<H2><A name="compat">Compatibility with Previous Servers</A></H2>

<H2><A NAME="compat">Compatibility with Previous Servers</A></H2>



<P>It may be necessary for a script that was designed for earlier

versions of Apache or other servers to need the information that the

docs/manual/cgi_path.html.en

+4 −4
Changes for docs/manual/cgi_path.html.en: 4 added lines, 4 removed lines.
Original line number Diff line number Diff line
@@ -16,7 +16,7 @@ 


<HR>



<H2><A name="over">Overview</A></H2>

<H2><A NAME="over">Overview</A></H2>



<P>As implemented in Apache 1.1.1 and earlier versions, the method

Apache used to create PATH_INFO in the CGI environment was
@@ -27,7 +27,7 @@ applications, the Apache 1.2 behavior is still compatible with the 
CGI/1.1 specification, and CGI scripts can be easily modified (<A

HREF="#compat">see below</A>).



<H2><A name="prob">The Problem</A></H2>

<H2><A NAME="prob">The Problem</A></H2>



<P>Apache 1.1.1 and earlier implemented the PATH_INFO and SCRIPT_NAME

environment variables by looking at the filename, not the URL. While
@@ -46,7 +46,7 @@ SCRIPT_NAME to "<CODE>/cgi-</CODE>". Obviously, the latter is 
incorrect. In certain cases, this could even cause the server to

crash.</P>



<H2><A name="solution">The Solution</A></H2>

<H2><A NAME="solution">The Solution</A></H2>



<P>Apache 1.2 and later now determine SCRIPT_NAME and PATH_INFO by

looking directly at the URL, and determining how much of the URL is
@@ -67,7 +67,7 @@ sort of information is not a recommended method, and a script making 
use of it "deserves" not to work. Apache 1.2b3 and later, however, do

provide <A HREF="#compat">a workaround.</A>



<H2><A name="compat">Compatibility with Previous Servers</A></H2>

<H2><A NAME="compat">Compatibility with Previous Servers</A></H2>



<P>It may be necessary for a script that was designed for earlier

versions of Apache or other servers to need the information that the

docs/manual/content-negotiation.html

+6 −4
Changes for docs/manual/content-negotiation.html: 6 added lines, 4 removed lines.
Original line number Diff line number Diff line
@@ -294,7 +294,8 @@ remains, move onto the next test. 
<LI>Select the variants with the highest language quality factor



<LI>Select the variants with the best language match, using either the

  order of languages on the <CODE>LanguagePriority</CODE> directive (if present),

  order of languages on the <CODE>LanguagePriority</CODE> directive (if

  present),

  else the order of languages on the Accept-Language header.



<LI>Select the variants with the highest 'level' media parameter
@@ -330,7 +331,7 @@ and go to stage 3. 


</OL>



<H2><A name="better">Fiddling with Quality Values</A></H2>

<H2><A NAME="better">Fiddling with Quality Values</A></H2>



<P>

Apache sometimes changes the quality values from what would be
@@ -435,10 +436,11 @@ Examples: 
</UL>



<P>

Here some more examples of filenames together with valid and invalid hyperlinks:

Here some more examples of filenames together with valid and invalid

hyperlinks:

</P>



<table border=1 cellpadding=8 cellspacing=0>

<TABLE BORDER=1 CELLPADDING=8 CELLSPACING=0>

<TR>

 <TH>Filename</TH>

 <TH>Valid hyperlink</TH>