Another pass at the normalisation of the HTML tags. Some

 ALINK="#FF0000"

>

<!--#include virtual="header.html" -->

<h1 ALIGN="CENTER">Setting which addresses and ports Apache uses</H1>

<H1 ALIGN="CENTER">Setting which addresses and ports Apache uses</H1>

<HR>

  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="directive-dict.html#Syntax"

 REL="Help"

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="directive-dict.html#Syntax"

 REL="Help"

   Listen 192.170.2.5:8000

</PRE>

<h2>How this works with Virtual Hosts</h2>

<H2>How this works with Virtual Hosts</H2>

BindAddress and Listen do not implement Virtual Hosts. They tell the

main server what addresses and ports to listen to.  If no

<VirtualHost> is set for an address and port that the server is

not listening to, it cannot be accessed.

<h2>See also</h2>

<H2>See also</H2>

See also the documentation on

<A HREF="vhosts/index.html">Virtual Hosts</A>,

 ALINK="#FF0000"

>

<!--#include virtual="header.html" -->

<h1 ALIGN="CENTER">Setting which addresses and ports Apache uses</H1>

<H1 ALIGN="CENTER">Setting which addresses and ports Apache uses</H1>

<HR>

  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="directive-dict.html#Syntax"

 REL="Help"

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="directive-dict.html#Syntax"

 REL="Help"

   Listen 192.170.2.5:8000

</PRE>

<h2>How this works with Virtual Hosts</h2>

<H2>How this works with Virtual Hosts</H2>

BindAddress and Listen do not implement Virtual Hosts. They tell the

main server what addresses and ports to listen to.  If no

<VirtualHost> is set for an address and port that the server is

not listening to, it cannot be accessed.

<h2>See also</h2>

<H2>See also</H2>

See also the documentation on

<A HREF="vhosts/index.html">Virtual Hosts</A>,

 ALINK="#FF0000"

>

<!--#include virtual="header.html" -->

<h1 ALIGN="CENTER">PATH_INFO Changes in the CGI Environment</H1>

<H1 ALIGN="CENTER">PATH_INFO Changes in the CGI Environment</H1>

<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

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

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

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

 ALINK="#FF0000"

>

<!--#include virtual="header.html" -->

<h1 ALIGN="CENTER">PATH_INFO Changes in the CGI Environment</H1>

<H1 ALIGN="CENTER">PATH_INFO Changes in the CGI Environment</H1>

<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

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

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

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

 ALINK="#FF0000"

>

<!--#include virtual="header.html" -->

<h1 ALIGN="CENTER">Content Negotiation</H1>

<H1 ALIGN="CENTER">Content Negotiation</H1>

<P>

Apache's support for content negotiation has been updated to meet the

<HR>

<h2>About Content Negotiation</h2>

<H2>About Content Negotiation</H2>

<P>

A resource may be available in several different representations. For

or <STRONG>variants</STRONG>. The ways in which the variants for a particular

resource vary are called the <STRONG>dimensions</STRONG> of negotiation.

<h2>Negotiation in Apache</h2>

<H2>Negotiation in Apache</H2>

<P>

In order to negotiate a resource, the server needs to be given

       filename pattern match, and chooses from among the results.

</UL>

<h3>Using a type-map file</h3>

<H3>Using a type-map file</H3>

<P>

A type map is a document which is associated with the handler

       thresholds without checking the actual file.

</DL>

<h3>Multiviews</h3>

<H3>Multiviews</H3>

<P>

This is a per-directory option, meaning it can be set with an

quality rating, which generally causes one of the other views (if any)

to be retrieved.

<h2>The Negotiation Algorithm</h2>

<H2>The Negotiation Algorithm</H2>

After Apache has obtained a list of the variants for a given resource,

either from a type-map file or from the filenames in the directory, it

particular dimension to achieve a better result. The ways Apache can

fiddle quality factors is explained in more detail below.

<h3>Dimensions of Negotiation</h3>

<H3>Dimensions of Negotiation</H3>

<TABLE>

<TR><TH>Dimension

can indicate a charset as a parameter of the media type.

</TABLE>

<h3>Apache Negotiation Algorithm</h3>

<H3>Apache Negotiation Algorithm</H3>

<P>

Apache uses an algorithm to select the 'best' variant (if any) to

</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

be applied.

<P>

<h3>Media Types and Wildcards</h3>

<H3>Media Types and Wildcards</H3>

<P>

The Accept: request header indicates preferences for media types. It

these special values are <EM>not</EM> applied, so requests from browsers

which send the correct information to start with work as expected.

<h3>Variants with no Language</h3>

<H3>Variants with no Language</H3>

<P>

If some of the variants for a particular resource have a language

or foo.fr.html will be returned. If the browser does not list

either en or fr as acceptable, foo.html will be returned instead.

<h2>Note on hyperlinks and naming conventions</h2>

<H2>Note on hyperlinks and naming conventions</H2>

<P>

If you are using language negotiation you can choose between

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

<h2>Note on Caching</h2>

<H2>Note on Caching</H2>

<P>

When a cache stores a document, it associates it with the request URL.