</div>
<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#namevip">Name-based vs. IP-based Virtual Hosts</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#using">Using Name-based Virtual Hosts</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#compat">Compatibility with Older Browsers</a></li>
-</ul><h3>See also</h3><ul class="seealso"><li><a href="ip-based.html">IP-based Virtual Host Support</a></li><li><a href="details.html">An In-Depth Discussion of Virtual Host Matching</a></li><li><a href="mass.html">Dynamically configured mass virtual hosting</a></li><li><a href="examples.html">Virtual Host examples for common setups</a></li><li><a href="examples.html#serverpath">ServerPath configuration example</a></li></ul></div>
+</ul><h3>See also</h3><ul class="seealso"><li><a href="ip-based.html">IP-based Virtual Host Support</a></li><li><a href="details.html">An In-Depth Discussion of Virtual Host Matching</a></li><li><a href="mass.html">Dynamically configured mass virtual hosting</a></li><li><a href="examples.html">Virtual Host examples for common setups</a></li></ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="namevip" id="namevip">Name-based vs. IP-based Virtual Hosts</a></h2>
<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
+ 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
+ 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
+ <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
<div class="section">
<h2><a name="using" id="using">Using Name-based Virtual Hosts</a></h2>
-<table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="../mod/core.html">core</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li><li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></td></tr></table>
+<table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="../mod/core.html">core</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="../mod/core.html#namevirtualhost">NameVirtualHost</a></code></li><li><code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code></li><li><code class="directive"><a href="../mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code></li></ul></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
in a <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>
container and list it first in the configuration file.</p>
-</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="section">
-<h2><a name="compat" id="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>
-
- <div class="note"><h3>How much older?</h3>
- <p>Please note that when we say older, we really do mean older. You are
- very unlikely to encounter one of these browsers in use today. All
- current versions of any browser send the <code>Host</code> header as
- required for name-based virtual hosts.</p>
- </div>
-
- <p>There is a possible workaround with the <code class="directive"><a href="../mod/core.html#serverpath">ServerPath</a></code>
- directive, albeit a slightly cumbersome one:</p>
-
- <p>Example configuration:</p>
-
- <div class="example"><p><code>
- NameVirtualHost 111.22.33.44<br />
- <br />
- <VirtualHost 111.22.33.44><br />
- <span class="indent">
- ServerName www.domain.tld<br />
- ServerPath /domain<br />
- DocumentRoot /web/domain<br />
- </span>
- </VirtualHost><br />
- </code></p></div>
-
- <p>What does this mean? It means that a request for any URI
- beginning with "<code>/domain</code>" will be served from the
- virtual host <code>www.domain.tld</code>. This means that the
- pages can be accessed as <code>http://www.domain.tld/domain/</code>
- for all clients, although clients sending a <code>Host:</code> 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
- <code>http://www.domain.tld/domain/</code>. Then, in the virtual
- host's pages, be sure to use either purely relative links
- (<em>e.g.</em>, "<code>file.html</code>" or
- "<code>../icons/image.gif</code>") or links containing the
- prefacing <code>/domain/</code> (<em>e.g.</em>,
- "<code>http://www.domain.tld/domain/misc/file.html</code>" or
- "<code>/domain/misc/file.html</code>").</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>
-
</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
<seealso><a href="details.html">An In-Depth Discussion of Virtual Host Matching</a></seealso>
<seealso><a href="mass.html">Dynamically configured mass virtual hosting</a></seealso>
<seealso><a href="examples.html">Virtual Host examples for common setups</a></seealso>
-<seealso><a href="examples.html#serverpath">ServerPath configuration example</a></seealso>
<section id="namevip"><title>Name-based vs. IP-based Virtual Hosts</title>
<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
+ 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
+ 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
+ <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
<directive module="core">NameVirtualHost</directive>
<directive module="core">ServerAlias</directive>
<directive module="core">ServerName</directive>
- <directive module="core">ServerPath</directive>
<directive module="core" type="section">VirtualHost</directive>
</directivelist>
</related>
</section>
-<section id="compat"><title>Compatibility with Older Browsers</title>
-
- <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>
-
- <note><title>How much older?</title>
- <p>Please note that when we say older, we really do mean older. You are
- very unlikely to encounter one of these browsers in use today. All
- current versions of any browser send the <code>Host</code> header as
- required for name-based virtual hosts.</p>
- </note>
-
- <p>There is a possible workaround with the <directive
- module="core">ServerPath</directive>
- directive, albeit a slightly cumbersome one:</p>
-
- <p>Example configuration:</p>
-
- <example>
- NameVirtualHost 111.22.33.44<br />
- <br />
- <VirtualHost 111.22.33.44><br />
- <indent>
- ServerName www.domain.tld<br />
- ServerPath /domain<br />
- DocumentRoot /web/domain<br />
- </indent>
- </VirtualHost><br />
- </example>
-
- <p>What does this mean? It means that a request for any URI
- beginning with "<code>/domain</code>" will be served from the
- virtual host <code>www.domain.tld</code>. This means that the
- pages can be accessed as <code>http://www.domain.tld/domain/</code>
- for all clients, although clients sending a <code>Host:</code> 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
- <code>http://www.domain.tld/domain/</code>. Then, in the virtual
- host's pages, be sure to use either purely relative links
- (<em>e.g.</em>, "<code>file.html</code>" or
- "<code>../icons/image.gif</code>") or links containing the
- prefacing <code>/domain/</code> (<em>e.g.</em>,
- "<code>http://www.domain.tld/domain/misc/file.html</code>" or
- "<code>/domain/misc/file.html</code>").</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>
-
-</section>
</manualpage>
projects / apache / commitdiff