Commit 22715103 authored by Yoshiki Hayashi's avatar Yoshiki Hayashi
Browse files

New Japanese translations. Forward port from 1.3. 


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

docs/manual/vhosts/fd-limits.html

deleted100644 → 0
+0 −73
Original line number Diff line number Diff line 
<!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>Apache Server Virtual Host Support</title>

  </head>

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



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

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

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



    <h1 align="CENTER">File Descriptor Limits</h1>



    <p>When using a large number of Virtual Hosts, Apache may run

    out of available file descriptors (sometimes called <cite>file

    handles</cite> if each Virtual Host specifies different log

    files. The total number of file descriptors used by Apache is

    one for each distinct error log file, one for every other log

    file directive, plus 10-20 for internal use. Unix operating

    systems limit the number of file descriptors that may be used

    by a process; the limit is typically 64, and may usually be

    increased up to a large hard-limit.</p>



    <p>Although Apache attempts to increase the limit as required,

    this may not work if:</p>



    <ol>

      <li>Your system does not provide the setrlimit() system

      call.</li>



      <li>The setrlimit(RLIMIT_NOFILE) call does not function on

      your system (such as Solaris 2.3)</li>



      <li>The number of file descriptors required exceeds the hard

      limit.</li>



      <li>Your system imposes other limits on file descriptors,

      such as a limit on stdio streams only using file descriptors

      below 256. (Solaris 2)</li>

    </ol>

    In the event of problems you can: 



    <ul>

      <li>Reduce the number of log files; don't specify log files

      in the VirtualHost sections, but only log to the main log

      files.</li>



      <li>

        If you system falls into 1 or 2 (above), then increase the

        file descriptor limit before starting Apache, using a

        script like 



        <blockquote>

          <code>#!/bin/sh<br />

           ulimit -S -n 100<br />

           exec httpd</code>

        </blockquote>

      </li>

    </ul>



    <p>Please see the <a

    href="../misc/descriptors.html">Descriptors and Apache</a>

    document containing further details about file descriptor

    problems and how they can be solved on your operating

    system.</p>

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

  </body>

</html>

docs/manual/vhosts/fd-limits.html.ja.jis

0 → 100644
+72 −0
Original line number Diff line number Diff line 
<?xml version="1.0" encoding="iso-2022-jp"?>

<!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" xml:lang="ja" lang="ja">

  <head>



    <title>Apache $B%5!<%P$N%P!<%A%c%k%[%9%H$N%5%]!<%H(B</title>

    <!-- English revision: 1.4 -->

  </head>

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



  <body bgcolor="#ffffff" text="#000000" link="#0000ff"

  vlink="#000080" alink="#ff0000">

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



    <h1 align="center">$B%U%!%$%k5-=R;R$N8B3&(B</h1>



    <p>$B$?$/$5$s$N%P!<%A%c%k%[%9%H$r1?MQ$9$k>l9g!"$b$7!"(B

    $B3F%P!<%A%c%k%[%9%H$4$H$K0[$J$k%m%0%U%!%$%k$,;XDj$7$F$"$k$H!"(B

    Apache $B$,%U%!%$%k5-=R;R(B (<cite>$B%U%!%$%k%O%s%I%k(B</cite>$B$H$b8F$P$l$^$9(B)

    $B$r;H$$@Z$C$F$7$^$&$3$H$,$"$j$^$9!#(BApache $B$,;HMQ$9$k%U%!%$%k(B

    $B5-=R;R$N?t$O!"3F%(%i!<%m%0%U%!%$%k$K$D$-(B 1 $B$D!"B>$N%m%0%U%!%$%k$N(B

    $B%G%#%l%/%F%#%V$K$D$-(B 1 $B$D!"$5$i$KFbIt$G;HMQ$9$k(B 10 $B$+$i(B 20$B!"(B

    $B$N9g7W$K$J$j$^$9!#(BUnix $B%*%Z%l!<%F%#%s%0%7%9%F%`$G$O%W%m%;%9$4$H$K(B

    $B;HMQ2DG=$J%U%!%$%k5-=R;R$N?t$r@)8B$7$F$$$^$9!#$?$$$F$$$N>l9g$O(B 64 $B$G!"(B

    $BIaDL$OBg$-$JCM$N%O!<%I%j%_%C%H$^$GA}$d$9$3$H$,$G$-$^$9!#(B</p>



    <p>Apache $B$OI,MW$K1~$8$F>e8B$r3HBg$7$h$&$H;n$_$^$9$,!"(B

    $B0J2<$N$h$&$J>l9g$K$O$&$^$/$$$+$J$$$+$b$7$l$^$;$s!#(B</p>



    <ol>

      <li>$BMxMQ$7$F$$$k%7%9%F%`$G(B setrlimit()

      $B%7%9%F%`%3!<%k$,Ds6!$5$l$F$$$J$$!#(B</li>



      <li>$B%7%9%F%`>e$G(B setrlimit(RLIMIT_NOFILE) $B$,F0:n$7$J$$(B

      ($B$?$H$($P(B Solaris 2.3 $B$N$h$&$K(B)$B!#(B</li>



      <li>$BMW5a$5$l$k%U%!%$%k5-=R;R$N?t$,(B

      $B%O!<%I%j%_%C%H$rD6$($F$7$^$&!#(B</li>



      <li>$B%7%9%F%`$K%U%!%$%k5-=R;R$K4X$7$FJL$N@)8B$,B8:_$7$F$7$^$C$F$$$k!#(B

      $B$?$H$($P!"(Bstdio $B%9%H%j!<%`$G$O%U%!%$%k5-=R;R$r(B 256 $B0J>e;H$($J$$(B

      (Solaris 2)$B!"$J$I!#(B</li>

    </ol>

    $BLdBj$,H/@8$7$?;~$K<h$jF@$kBP=hJ}K!$O<!$N$H$*$j(B:



    <ul>

      <li>$B%m%0%U%!%$%k$N?t$r8:$i$9!#(BVirtualHost

      $B%;%/%7%g%s$G%m%0%U%!%$%k$r;XDj$;$:!"(B

      $B%a%$%s$N%m%0%U%!%$%k$K$N$_5-O?$9$k!#(B</li>



      <li>

        $B$b$7!"A0=R$N(B 1 $B$^$?$O(B 2 $B$N>l9g$G$"$l$P!"(B

        Apache $B$r5/F0$9$kA0$K%U%!%$%k5-=R;R$rA}$d$7$^$9!#(B

        $B$?$H$($P<!$N$h$&$J%9%/%j%W%H$r;H$$$^$9!#(B



        <blockquote>

          <code>#!/bin/sh <br />

           ulimit -S -n 100 <br />

           exec httpd</code>

        </blockquote>

      </li>

    </ul>



    <p>$B%U%!%$%k5-=R;R$NLdBj$K$D$$$F$N>\:Y$d!"(B

    $B%*%Z%l!<%F%#%s%0%7%9%F%`$4$H$N2r7hJ}K!$K$D$$$F$O!V(B<a

    href="../misc/descriptors.html">$B%U%!%$%k5-=R;R$H(B

    Apache</a>$B!W$NJ8=q$r;2>H$7$F$/$@$5$$!#(B

    </p>

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

  </body>

</html>

docs/manual/vhosts/index.html

deleted100644 → 0
+0 −84
Original line number Diff line number Diff line 
<!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>Apache Virtual Host documentation</title>

  </head>

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



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

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

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



    <h1 align="CENTER">Apache Virtual Host documentation</h1>



    <p>The term <cite>Virtual Host</cite> refers to the practice of

    maintaining more than one server on one machine, as

    differentiated by their apparent hostname. For example, it is

    often desirable for companies sharing a web server to have

    their own domains, with web servers accessible as

    <samp>www.company1.com</samp> and

    <samp>www.company2.com</samp>, without requiring the user to

    know any extra path information.</p>



    <p>Apache was one of the first servers to support IP-based

    virtual hosts right out of the box. Versions 1.1 and later of

    Apache support both, IP-based and name-based virtual hosts

    (vhosts). The latter variant of virtual hosts is sometimes also

    called host-based or non-IP virtual hosts.</p>



    <p>Below is a list of documentation pages which explain all

    details of virtual host support in Apache version 1.3 and

    later.</p>

    <hr />



    <h2>Virtual Host Support</h2>



    <ul>

      <li><a href="name-based.html">Name-based Virtual

      Hosts</a></li>



      <li><a href="ip-based.html">IP-based Virtual Hosts</a></li>



      <li><a href="examples.html">Virtual Host examples for common

      setups</a></li>



      <li><a href="details.html">In-Depth Discussion of Virtual

      Host Matching</a></li>



      <li><a href="fd-limits.html">File Descriptor Limits</a></li>



      <li><a href="mass.html">Dynamically Configured Mass Virtual

      Hosting</a></li>

    </ul>



    <h2>Configuration directives</h2>



    <ul>

      <li><a

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



      <li><a

      href="../mod/core.html#namevirtualhost">NameVirtualHost</a></li>



      <li><a href="../mod/core.html#servername">ServerName</a></li>



      <li><a

      href="../mod/core.html#serveralias">ServerAlias</a></li>



      <li><a href="../mod/core.html#serverpath">ServerPath</a></li>

    </ul>



    <p>Folks trying to debug their virtual host configuration may

    find the Apache <code>-t -D DUMP_VHOSTS</code> command line switch 

    useful. It will dump out a description of how Apache parsed the

    configuration file. Careful examination of the IP addresses and

    server names may help uncover configuration mistakes. 

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

    </p>

  </body>

</html>

docs/manual/vhosts/index.html.ja.jis

0 → 100644
+82 −0
Original line number Diff line number Diff line 
<?xml version="1.0" encoding="iso-2022-jp"?>

<!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" xml:lang="ja" lang="ja">

  <head>



    <title>Apache $B%P!<%A%c%k%[%9%H@bL@=q(B</title>

    <!-- English revision: 1.9 -->

  </head>



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

  <body bgcolor="#ffffff" text="#000000" link="#0000ff"

  vlink="#000080" alink="#ff0000">

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



    <h1 align="center">Apache $B%P!<%A%c%k%[%9%H@bL@=q(B</h1>



    <p><cite>$B%P!<%A%c%k%[%9%H(B</cite>$B$H$$$&MQ8l$O!"(B1 $BBf$N%^%7%s>e$G(B

    $B0l$D0J>e$N%5!<%P$r!"(B

    $B$=$l$>$lJL$N0c$&%[%9%HL>$G8+$;$k1?MQJ}K!$N$3$H$r;X$7$^$9!#(B

    $B$?$H$($P!"0l$D$N%5!<%P$r6&M-$9$kJ#?t$N2q<R$,!"(B

    $B%f!<%6$KM>7W$J%Q%9L>$rMW5a$;$:$K!"(B<samp>www.company1.com</samp>

    $B$d(B <samp>www.company2.com</samp> $B$H$$$C$?$=$l$>$l$K8GM-$N(B

    $B%I%a%$%sL>$G%&%'%V%5!<%P$K%"%/%;%9$G$-$k$h$&$K$7$?$$!"(B

    $B$H$$$C$?$3$H$O$7$P$7$P$"$j$^$9!#(B</p>



    <p>Apache $B$O!"FC$K<j$rF~$l$J$$>uBV$G(B IP $B%Y!<%9$N%P!<%A%c%k%[%9%H(B

    $B$r%5%]!<%H$7$?:G=i$N%5!<%P$N0l$D$G$9!#%P!<%8%g%s(B 1.1 $B0J9_$N(B Apache

    $B$G$O!"(BIP $B%Y!<%9$H%M!<%`%Y!<%9$N%P!<%A%c%k%[%9%H$NN>J}$r%5%]!<%H(B

    $B$7$F$$$^$9!#%M!<%`%Y!<%9$N%P!<%A%c%k%[%9%H$O!"%[%9%H%Y!<%9$"$k$$$OHs(B

    IP $B%Y!<%9$N%P!<%A%c%k%[%9%H$H8F$P$l$k$3$H$b$"$j$^$9!#(B</p>



    <p>$B0J2<$N%Z!<%8$G$O!"(BApache $B%P!<%8%g%s(B 1.3

    $B0J9_$G$N%P!<%A%c%k%[%9%H$N%5%]!<%H$K$D$$$F$N>\:Y$r@bL@$7$^$9!#(B</p>



    <hr />



    <h2>$B%P!<%A%c%k%[%9%H$N%5%]!<%H(B</h2>



    <ul>

      <li><a

     href="name-based.html">$B%M!<%`%Y!<%9$N%P!<%A%c%k%[%9%H(B</a></li>



      <li><a href="ip-based.html">IP $B%Y!<%9$N%P!<%A%c%k%[%9%H(B</a></li>



      <li><a

     href="examples.html">$B%P!<%A%c%k%[%9%H$N0lHLE*$J@_DjNc(B</a></li>



      <li><a

     href="details.html">$B%P!<%A%c%k%[%9%H$N%^%C%A%s%0$K$D$$$F$N>\:Y(B</a></li>



      <li><a href="fd-limits.html">$B%U%!%$%k5-=R;R$N8B3&(B</a></li>



      <li><a

     href="mass.html">$BBgNL$N%P!<%A%c%k%[%9%H$NF0E*$J@_Dj(B</a></li>

    </ul>



    <h2>$B@_Dj%G%#%l%/%F%#%V(B</h2>



    <ul>

      <li><a

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



      <li><a

      href="../mod/core.html#namevirtualhost">NameVirtualHost</a></li>



      <li><a href="../mod/core.html#servername">ServerName</a></li>



      <li><a href="../mod/core.html#serveralias">ServerAlias</a></li>



      <li><a href="../mod/core.html#serverpath">ServerPath</a></li>

    </ul>





    <p>$B%P!<%A%c%k%[%9%H$N@_Dj$N%G%P%C%0$r$9$k$K$O(B

    Apache $B$N%3%^%s%I%i%$%s%9%$%C%A(B <code>-t -D DUMP_VHOSTS</code> $B$,JXMx$G$9!#(B

    Apache $B$,@_Dj%U%!%$%k$r$I$&2r@O$7$?$+$K$D$$$F=PNO$7$^$9!#(B

    IP $B%"%I%l%9$H%5!<%PL>$rCm0U?<$/D4$Y$l$P!"(B

    $B@_Dj$N4V0c$$$r8+$D$1$k=u$1$K$J$k$G$7$g$&!#(B</p>

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

  </body>

</html>

docs/manual/vhosts/name-based.html

deleted100644 → 0
+0 −231
Original line number Diff line number Diff line 
<!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>

    <title>Name-based Virtual Hosts</title>

  </head>

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



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

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

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



    <h1 align="CENTER">Name-based Virtual Host Support</h1>



<p>This document describes when and how to use name-based virtual hosts.</p>



<ul>

<li><a href="#namevip">Name-based vs. IP-based Virtual Hosts</a></li>

<li><a href="#using">Using Name-based Virtual Hosts</a></li>

<li><a href="#compat">Compatibility With Older Browsers</a></li>

</ul>



<p>See also: <a href="examples.html">Virtual Host examples for common

setups</a>, <a href="ip-based.html">IP-based Virtual Host Support</a>,

<a href="details.html">An In-Depth Discussion of Virtual Host

Matching</a>, and <a href="mass.html">Dynamically configured mass

virtual hosting</a>.</p>



<hr />



<h2><a name="namevip">Name-based vs. IP-based Virtual Hosts</a></h2>



<p>IP-based virtual hosts use the IP address of the connection to

determine the correct virtual host to serve.  Therefore you need to

have a separate IP address for each host.  With name-based virtual

hosting, the server relies on the client to report the hostname as

part of the HTTP headers.  Using this technique, many different hosts

can share the same IP address.</p>



<p>Name-based virtual hosting is usually simpler, since you need

only configure your DNS server to map each hostname to the correct

IP address and then configure the Apache HTTP Server to recognize

the different hostnames.  Name-based virtual hosting also eases

the demand for scarce IP addresses.  Therefore you should use

name-based virtual hosting unless there is a specific reason to

choose IP-based virtual hosting.  Some reasons why you might consider

using IP-based virtual hosting:</p>



<ul> 



<li>Some ancient clients are not compatible with name-based virtual

hosting.  For name-based virtual hosting to work, the client must send

the HTTP Host header.  This is required by HTTP/1.1, and is

implemented by all modern HTTP/1.0 browsers as an extension.  If you

need to support obsolete clients and still use name-based virtual

hosting, a possible technique is discussed at the end of this

document.</li>



<li>Name-based virtual hosting cannot be used with SSL secure servers

because of the nature of the SSL protocol.</li>



<li>Some operating systems and network equipment implement bandwidth

management techniques that cannot differentiate between hosts unless

they are on separate IP addresses.</li>



</ul>



<h2><a name="using">Using Name-based Virtual Hosts</a></h2>



<table border="1">

<tr><td align="top">

<strong>Related Directives</strong><br><br>



<a href="../mod/core.html#documentroot">DocumentRoot</a><br />

<a href="../mod/core.html#namevirtualhost">NameVirtualHost</a><br />

<a href="../mod/core.html#serveralias">ServerAlias</a><br />

<a href="../mod/core.html#servername">ServerName</a><br />

<a href="../mod/core.html#serverpath">ServerPath</a><br />

<a href="../mod/core.html#virtualhost">VirtualHost</a><br />

</td></tr></table>



<p>To use name-based virtual hosting, you must designate the IP

address (and possibly port) on the server that will be accepting

requests for the hosts.  This is configured using the <a

href="../mod/core.html#namevirtualhost">NameVirtualHost</a> directive.

In the normal case where any and all IP addresses on the server should

be used, you can use <code>*</code> as the argument to

<code>NameVirtualHost</code>.  Note that mentioning an IP address in a

<code>NameVirtualHost</code> directive does not automatically make the

server listen to that IP address.  See <a href="../bind.html">Setting

which addresses and ports Apache uses</a> for more details.  In addition,

any IP address specified here must be associated with a network interface

on the server.</p>



<p>The next step is to create a <a

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

each different host that you would like to serve.  The argument to the

<code>&lt;VirtualHost&gt;</code> directive should be the same as the

argument to the <code>NameVirtualHost</code> directive (ie, an IP

address, or <code>*</code> for all addresses).  Inside each

<code>&lt;VirtualHost&gt;</code> block, you will need at minimum a <a

href="../mod/core.html#servername">ServerName</a> directive to

designate which host is served and a <a

href="../mod/core.html#documentroot">DocumentRoot</a> directive to

show where in the filesystem the content for that host lives.</p>



<p>For example, suppose that both <samp>www.domain.tld</samp> and

<samp>www.otherdomain.tld</samp> point at an IP address

that the server is listening to.  Then you simply add the following

to <code>httpd.conf</code>:</p>



<pre>

    NameVirtualHost *



    &lt;VirtualHost *&gt;

    ServerName www.domain.tld

    DocumentRoot /www/domain

    &lt;/VirtualHost&gt;



    &lt;VirtualHost *&gt;

    ServerName www.otherdomain.tld

    DocumentRoot /www/otherdomain

    &lt;/VirtualHost&gt;

</pre>



<p>You can alternatively specify an explicit IP address in place of

the * in both the <code>NameVirtualHost</code> and

<code>&lt;VirtualHost&gt;</code> directives.</p>



<p>Many servers want to be accessible by more than one name.  This is

possible with the <a

href="../mod/core.html#serveralias"><code>ServerAlias</code></a>

directive, placed inside the &lt;VirtualHost&gt; section. For

example if you add this to the first &lt;VirtualHost&gt; block

above</p> 



<blockquote><code> 

ServerAlias domain.tld *.domain.tld

</code></blockquote>



<p>then requests for all hosts in the <code>domain.tld</code> domain

will be served by the <code>www.domain.tld</code> virtual host.  The

wildcard characters * and ? can be used to match names.  Of course,

you can't just make up names and place them in <code>ServerName</code>

or <code>ServerAlias</code>.  You must first have your DNS server

properly configured to map those names to an IP address associated

with your server.</p>



<p>Finally, you can fine-tune the configuration of the virtual hosts

by placing other directives inside the

<code>&lt;VirtualHost&gt;</code> containers.  Most directives can be

placed in these containers and will then change the configuration only

of the relevant virtual host.  To find out if a particular directive

is allowed, check the <a

href="../mod/directive-dist.html#Context">Context</a> of the

directive.  Configuration directives set in the <em>main server

context</em> (outside any <code>&lt;VirtualHost&gt;</code> container)

will be used only if they are not overriden by the virtual host

settings.</p>



<p>Now when a request arrives, the server will first check if it is

using an IP address that matches the <code>NameVirtualHost</code>.  If

it is, then it will look at each <code>&lt;VirtualHost&gt;</code>

section with a matching IP address and try to find one where the

<code>ServerName</code> or <code>ServerAlias</code> matches the

requested hostname.  If it finds one, then it uses the configuration

for that server.  If no matching virtual host is found, then

<strong>the first listed virtual host</strong> that matches the IP

address will be used.</p>



<p>As a consequence, the first listed virtual host is the

<em>default</em> virtual host.  The <code>DocumentRoot</code> from the

<em>main server</em> will <strong>never</strong> be used when an IP

address matches the <code>NameVirtualHost</code> directive.  If you

would like to have a special configuration for requests that do not

match any particular virtual host, simply put that configuration in a

<code>&lt;VirtualHost&gt;</code> container and list it first in the

configuration file.</p>



<h2><a name="compat">Compatibility with Older Browsers</a></h2>



    <p>As mentioned earlier, there are some clients 

    who do not send the required data for the name-based virtual

    hosts to work properly. These clients will always be sent the

    pages from the first virtual host listed for that IP address

    (the <cite>primary</cite> name-based virtual host).</p>



    <p>There is a possible workaround with the <a

    href="../mod/core.html#serverpath"><code>ServerPath</code></a>

    directive, albeit a slightly cumbersome one:</p>



    <p>Example configuration:</p>

<pre>

    NameVirtualHost 111.22.33.44



    &lt;VirtualHost 111.22.33.44&gt;

    ServerName www.domain.tld

    ServerPath /domain

    DocumentRoot /web/domain

    &lt;/VirtualHost&gt;

</pre>



    <p>What does this mean? It means that a request for any URI

    beginning with "<samp>/domain</samp>" will be served from the

    virtual host <samp>www.domain.tld</samp> This means that the

    pages can be accessed as

    <code>http://www.domain.tld/domain/</code> for all clients,

    although clients sending a <samp>Host:</samp> header can also

    access it as <code>http://www.domain.tld/</code>.</p>



    <p>In order to make this work, put a link on your primary

    virtual host's page to

    <samp>http://www.domain.tld/domain/</samp> Then, in the virtual

    host's pages, be sure to use either purely relative links

    (<em>e.g.</em>, "<samp>file.html</samp>" or

    "<samp>../icons/image.gif</samp>" or links containing the

    prefacing <samp>/domain/</samp> (<em>e.g.</em>,

    "<samp>http://www.domain.tld/domain/misc/file.html</samp>" or

    "<samp>/domain/misc/file.html</samp>").</p>



    <p>This requires a bit of discipline, but adherence to these

    guidelines will, for the most part, ensure that your pages will

    work with all browsers, new and old.</p>



    <p>See also: <a href="examples.html#serverpath">ServerPath

    configuration example</a></p>

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

  </body>

</html>