Commit c91df556 authored by Richard Bowen's avatar Richard Bowen
Browse files

Ran w3c tidy on these as 'tidy -mi -asxml' to get xhtml. Please verify, 

in particular, the non-english files, to make sure I did not screw
anything up. They look fine to me.


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

docs/manual/bind.html

+67 −66
Original line number Diff line number Diff line 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML><HEAD>

<TITLE>Setting which addresses and ports Apache uses</TITLE>

</HEAD>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">



<html xmlns="http://www.w3.org/1999/xhtml">

  <head>

    <meta name="generator" content="HTML Tidy, see www.w3.org" />



    <title>Setting which addresses and ports Apache uses</title>

  </head>

  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->

<BODY

 BGCOLOR="#FFFFFF"

 TEXT="#000000"

 LINK="#0000FF"

 VLINK="#000080"

 ALINK="#FF0000"

>



  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"

  vlink="#000080" alink="#FF0000">

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

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



<p>When Apache starts, it connects to some port and address on the

local machine and waits for incoming requests. By default, it

listens to all addresses on the machine, and to the port

as specified by the <code>Port</code> directive in the server configuration.

However, it can be told to listen to more the one port, or to listen

to only selected addresses, or a combination. This is often combined

with the Virtual Host feature which determines how Apache

responds to different IP addresses, hostnames and ports.</p>

    <h1 align="CENTER">Setting which addresses and ports Apache

    uses</h1>



    <p>When Apache starts, it connects to some port and address on

    the local machine and waits for incoming requests. By default,

    it listens to all addresses on the machine, and to the port as

    specified by the <code>Port</code> directive in the server

    configuration. However, it can be told to listen to more the

    one port, or to listen to only selected addresses, or a

    combination. This is often combined with the Virtual Host

    feature which determines how Apache responds to different IP

    addresses, hostnames and ports.</p>



    <p>The <code>Listen</code> directive tells the server to accept

incoming requests only on the specified port or address-and-port

combinations. If only a port number is specified in the

<code>Listen</code> directive, the server listens to the given port on

all interfaces, instead of the port given by the <code>Port</code>

directive. If an IP address is given as well as a port, the server

will listen on the given port and interface.  Multiple Listen

directives may be used to specify a number of addresses and ports to

listen to. The server will respond to requests from any of the listed

addresses and ports.</P>

    incoming requests only on the specified port or

    address-and-port combinations. If only a port number is

    specified in the <code>Listen</code> directive, the server

    listens to the given port on all interfaces, instead of the

    port given by the <code>Port</code> directive. If an IP address

    is given as well as a port, the server will listen on the given

    port and interface. Multiple Listen directives may be used to

    specify a number of addresses and ports to listen to. The

    server will respond to requests from any of the listed

    addresses and ports.</p>



<p>For example, to make the server accept connections on both port

80 and port 8000, use:

<PRE>

    <p>For example, to make the server accept connections on both

    port 80 and port 8000, use:</p>

<pre>

   Listen 80

   Listen 8000

</PRE>



</pre>

    To make the server accept connections on two specified

    interfaces and port numbers, use 

<PRE>

<pre>

   Listen 192.170.2.1:80

   Listen 192.170.2.5:8000

</PRE>

</pre>



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

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



    <p>Listen does not implement Virtual Hosts. It only tells the

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

&lt;VirtualHost&gt; directives are used, the server will behave the

same for all accepted requests. However, &lt;VirtualHost&gt; can be

used to specify a different behavior for one or more of the addresses

and ports. To implement a VirtualHost, the server must first be told

to listen to the address and port to be used. Then a

&lt;VirtualHost&gt; section should be created for a specified address

and port to set the behavior of this virtual host. Note that if the

&lt;VirtualHost&gt; is set for an address and port that the server is

not listening to, it cannot be accessed.



<H2>See also</H2>



See also the documentation on

<a href="mod/mpm_common.html#listen">Listen directive</a>,

<A HREF="vhosts/">Virtual Hosts</A>,

<A HREF="mod/core.html#port">Port directive</A>,

<A HREF="dns-caveats.html">DNS Issues</A>

and

<A HREF="mod/core.html#virtualhost">&lt;VirtualHost&gt; section</A>.

    &lt;VirtualHost&gt; directives are used, the server will behave

    the same for all accepted requests. However,

    &lt;VirtualHost&gt; can be used to specify a different behavior

    for one or more of the addresses and ports. To implement a

    VirtualHost, the server must first be told to listen to the

    address and port to be used. Then a &lt;VirtualHost&gt; section

    should be created for a specified address and port to set the

    behavior of this virtual host. Note that if the

    &lt;VirtualHost&gt; is set for an address and port that the

    server is not listening to, it cannot be accessed.</p>



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

</BODY>

</HTML>

    <h2>See also</h2>

    See also the documentation on <a

    href="mod/mpm_common.html#listen">Listen directive</a>, <a

    href="vhosts/">Virtual Hosts</a>, <a

    href="mod/core.html#port">Port directive</a>, <a

    href="dns-caveats.html">DNS Issues</a> and <a

    href="mod/core.html#virtualhost">&lt;VirtualHost&gt;

    section</a>. <!--#include virtual="footer.html" -->

  </body>

</html>

docs/manual/bind.html.en

+67 −66
Original line number Diff line number Diff line 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML><HEAD>

<TITLE>Setting which addresses and ports Apache uses</TITLE>

</HEAD>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">



<html xmlns="http://www.w3.org/1999/xhtml">

  <head>

    <meta name="generator" content="HTML Tidy, see www.w3.org" />



    <title>Setting which addresses and ports Apache uses</title>

  </head>

  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->

<BODY

 BGCOLOR="#FFFFFF"

 TEXT="#000000"

 LINK="#0000FF"

 VLINK="#000080"

 ALINK="#FF0000"

>



  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"

  vlink="#000080" alink="#FF0000">

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

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



<p>When Apache starts, it connects to some port and address on the

local machine and waits for incoming requests. By default, it

listens to all addresses on the machine, and to the port

as specified by the <code>Port</code> directive in the server configuration.

However, it can be told to listen to more the one port, or to listen

to only selected addresses, or a combination. This is often combined

with the Virtual Host feature which determines how Apache

responds to different IP addresses, hostnames and ports.</p>

    <h1 align="CENTER">Setting which addresses and ports Apache

    uses</h1>



    <p>When Apache starts, it connects to some port and address on

    the local machine and waits for incoming requests. By default,

    it listens to all addresses on the machine, and to the port as

    specified by the <code>Port</code> directive in the server

    configuration. However, it can be told to listen to more the

    one port, or to listen to only selected addresses, or a

    combination. This is often combined with the Virtual Host

    feature which determines how Apache responds to different IP

    addresses, hostnames and ports.</p>



    <p>The <code>Listen</code> directive tells the server to accept

incoming requests only on the specified port or address-and-port

combinations. If only a port number is specified in the

<code>Listen</code> directive, the server listens to the given port on

all interfaces, instead of the port given by the <code>Port</code>

directive. If an IP address is given as well as a port, the server

will listen on the given port and interface.  Multiple Listen

directives may be used to specify a number of addresses and ports to

listen to. The server will respond to requests from any of the listed

addresses and ports.</P>

    incoming requests only on the specified port or

    address-and-port combinations. If only a port number is

    specified in the <code>Listen</code> directive, the server

    listens to the given port on all interfaces, instead of the

    port given by the <code>Port</code> directive. If an IP address

    is given as well as a port, the server will listen on the given

    port and interface. Multiple Listen directives may be used to

    specify a number of addresses and ports to listen to. The

    server will respond to requests from any of the listed

    addresses and ports.</p>



<p>For example, to make the server accept connections on both port

80 and port 8000, use:

<PRE>

    <p>For example, to make the server accept connections on both

    port 80 and port 8000, use:</p>

<pre>

   Listen 80

   Listen 8000

</PRE>



</pre>

    To make the server accept connections on two specified

    interfaces and port numbers, use 

<PRE>

<pre>

   Listen 192.170.2.1:80

   Listen 192.170.2.5:8000

</PRE>

</pre>



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

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



    <p>Listen does not implement Virtual Hosts. It only tells the

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

&lt;VirtualHost&gt; directives are used, the server will behave the

same for all accepted requests. However, &lt;VirtualHost&gt; can be

used to specify a different behavior for one or more of the addresses

and ports. To implement a VirtualHost, the server must first be told

to listen to the address and port to be used. Then a

&lt;VirtualHost&gt; section should be created for a specified address

and port to set the behavior of this virtual host. Note that if the

&lt;VirtualHost&gt; is set for an address and port that the server is

not listening to, it cannot be accessed.



<H2>See also</H2>



See also the documentation on

<a href="mod/mpm_common.html#listen">Listen directive</a>,

<A HREF="vhosts/">Virtual Hosts</A>,

<A HREF="mod/core.html#port">Port directive</A>,

<A HREF="dns-caveats.html">DNS Issues</A>

and

<A HREF="mod/core.html#virtualhost">&lt;VirtualHost&gt; section</A>.

    &lt;VirtualHost&gt; directives are used, the server will behave

    the same for all accepted requests. However,

    &lt;VirtualHost&gt; can be used to specify a different behavior

    for one or more of the addresses and ports. To implement a

    VirtualHost, the server must first be told to listen to the

    address and port to be used. Then a &lt;VirtualHost&gt; section

    should be created for a specified address and port to set the

    behavior of this virtual host. Note that if the

    &lt;VirtualHost&gt; is set for an address and port that the

    server is not listening to, it cannot be accessed.</p>



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

</BODY>

</HTML>

    <h2>See also</h2>

    See also the documentation on <a

    href="mod/mpm_common.html#listen">Listen directive</a>, <a

    href="vhosts/">Virtual Hosts</a>, <a

    href="mod/core.html#port">Port directive</a>, <a

    href="dns-caveats.html">DNS Issues</a> and <a

    href="mod/core.html#virtualhost">&lt;VirtualHost&gt;

    section</a>. <!--#include virtual="footer.html" -->

  </body>

</html>

docs/manual/cgi_path.html

+94 −89
Original line number Diff line number Diff line 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<HTML><HEAD>

<TITLE>PATH_INFO Changes in the CGI Environment</TITLE>

</HEAD>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">



<html xmlns="http://www.w3.org/1999/xhtml">

  <head>

    <meta name="generator" content="HTML Tidy, see www.w3.org" />



    <title>PATH_INFO Changes in the CGI Environment</title>

  </head>

  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->

<BODY

 BGCOLOR="#FFFFFF"

 TEXT="#000000"

 LINK="#0000FF"

 VLINK="#000080"

 ALINK="#FF0000"

>



  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"

  vlink="#000080" alink="#FF0000">

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

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



<HR>



<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

counterintuitive, and could result in crashes in certain cases. In

Apache 1.2 and beyond, this behavior has changed. Although this

results in some compatibility problems with certain legacy CGI

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>



<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

this resulted in the correct values in many cases, when the filesystem

path was overloaded to contain path information, it could result in

errant behavior. For example, if the following appeared in a config

file:

<PRE>



    <h1 align="CENTER">PATH_INFO Changes in the CGI

    Environment</h1>

    <hr />



    <h2><a id="over" 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 counterintuitive, and could result in crashes in certain

    cases. In Apache 1.2 and beyond, this behavior has changed.

    Although this results in some compatibility problems with

    certain legacy CGI 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>).</p>



    <h2><a id="prob" 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 this resulted in the correct values in many

    cases, when the filesystem path was overloaded to contain path

    information, it could result in errant behavior. For example,

    if the following appeared in a config file:</p>

<pre>

     Alias /cgi-ralph /usr/local/httpd/cgi-bin/user.cgi/ralph

</PRE>

<P>In this case, <CODE>user.cgi</CODE> is the CGI script, the "/ralph"

is information to be passed onto the CGI. If this configuration was in

place, and a request came for "<CODE>/cgi-ralph/script/</CODE>", the

code would set PATH_INFO to "<CODE>/ralph/script</CODE>", and

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>



<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

client-modifiable, and setting PATH_INFO to it. To use the above

example, PATH_INFO would be set to "<CODE>/script</CODE>", and

SCRIPT_NAME to "<CODE>/cgi-ralph</CODE>". This makes sense and results

in no server behavior problems. It also permits the script to be

</pre>



    <p>In this case, <code>user.cgi</code> is the CGI script, the

    "/ralph" is information to be passed onto the CGI. If this

    configuration was in place, and a request came for

    "<code>/cgi-ralph/script/</code>", the code would set PATH_INFO

    to "<code>/ralph/script</code>", and 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 id="solution" 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 client-modifiable, and setting PATH_INFO to it. To use

    the above example, PATH_INFO would be set to

    "<code>/script</code>", and SCRIPT_NAME to

    "<code>/cgi-ralph</code>". This makes sense and results in no

    server behavior problems. It also permits the script to be

    guaranteed that

"<CODE>http://$SERVER_NAME:$SERVER_PORT$SCRIPT_NAME$PATH_INFO</CODE>"

will always be an accessible URL that points to the current script,

something which was not necessarily true with previous versions of

Apache.



<P>However, the "<CODE>/ralph</CODE>"

information from the <CODE>Alias</CODE> directive is lost. This is

unfortunate, but we feel that using the filesystem to pass along this

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>



<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

old PATH_INFO variable provided. For this purpose, Apache 1.2 (1.2b3

and later) sets an additional variable, FILEPATH_INFO. This

environment variable contains the value that PATH_INFO would have had

with Apache 1.1.1.</P>



<P>A script that wishes to work with both Apache 1.2 and earlier

versions can simply test for the existence of FILEPATH_INFO, and use

it if available. Otherwise, it can use PATH_INFO. For example, in

Perl, one might use:

<PRE>

    $path_info = $ENV{'FILEPATH_INFO'} || $ENV{'PATH_INFO'};

</PRE>

    "<code>http://$SERVER_NAME:$SERVER_PORT$SCRIPT_NAME$PATH_INFO</code>"

    will always be an accessible URL that points to the current

    script, something which was not necessarily true with previous

    versions of Apache.</p>



    <p>However, the "<code>/ralph</code>" information from the

    <code>Alias</code> directive is lost. This is unfortunate, but

    we feel that using the filesystem to pass along this 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></p>



<P>By doing this, a script can work with all servers supporting the

CGI/1.1 specification, including all versions of Apache.</P>

    <h2><a id="compat" 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 old PATH_INFO variable provided. For this

    purpose, Apache 1.2 (1.2b3 and later) sets an additional

    variable, FILEPATH_INFO. This environment variable contains the

    value that PATH_INFO would have had with Apache 1.1.1.</p>



    <p>A script that wishes to work with both Apache 1.2 and

    earlier versions can simply test for the existence of

    FILEPATH_INFO, and use it if available. Otherwise, it can use

    PATH_INFO. For example, in Perl, one might use:</p>

<pre>

    $path_info = $ENV{'FILEPATH_INFO'} || $ENV{'PATH_INFO'};

</pre>



    <p>By doing this, a script can work with all servers supporting

    the CGI/1.1 specification, including all versions of

    Apache.</p>

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

</BODY>

</HTML>

  </body>

</html>

docs/manual/cgi_path.html.en

+94 −89

File changed.

Preview size limit exceeded, changes collapsed.

docs/manual/configuring.html.en

+244 −205

File changed.

Preview size limit exceeded, changes collapsed.