mirror of
https://github.com/apache/httpd.git
synced 2025-08-20 16:09:55 +00:00
87e54e707f
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1066484 13f79535-47bb-0310-9956-ffa450edef68
177 lines
13 KiB
XML
177 lines
13 KiB
XML
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
|
||
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|
||
This file is generated from xml source: DO NOT EDIT
|
||
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|
||
-->
|
||
<title>Name-based Virtual Host Support - Apache HTTP Server</title>
|
||
<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
|
||
<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
|
||
<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
|
||
<link href="../images/favicon.ico" rel="shortcut icon" /></head>
|
||
<body id="manual-page"><div id="page-header">
|
||
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
|
||
<p class="apache">Apache HTTP Server Version 2.3</p>
|
||
<img alt="" src="../images/feather.gif" /></div>
|
||
<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
|
||
<div id="path">
|
||
<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.3</a> > <a href="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>Name-based Virtual Host Support</h1>
|
||
<div class="toplang">
|
||
<p><span>Available Languages: </span><a href="../de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> |
|
||
<a href="../en/vhosts/name-based.html" title="English"> en </a> |
|
||
<a href="../fr/vhosts/name-based.html" hreflang="fr" rel="alternate" title="Fran<61>ais"> fr </a> |
|
||
<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
|
||
<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
|
||
<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="T<>rk<72>e"> tr </a></p>
|
||
</div>
|
||
|
||
<p>This document describes when and how to use name-based virtual hosts.</p>
|
||
</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="#alg">How the server selects the proper name-based virtual host</a></li>
|
||
<li><img alt="" src="../images/down.gif" /> <a href="#using">Using Name-based Virtual Hosts</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></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><a href="ip-based.html">IP-based virtual hosts</a> 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.</p>
|
||
|
||
<p>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 you are using equipment
|
||
that explicitly demands IP-based hosting. Historical reasons for
|
||
IP-based virtual hosting based on client support are no longer
|
||
applicable to a general-purpose web server.</p>
|
||
|
||
<p> Name-based virtual hosting builds off of the IP-based virtual host
|
||
selection algorithm, meaning that searches for the proper server name
|
||
occur only between virtual hosts that have the best IP-based address.</p>
|
||
|
||
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
|
||
<div class="section">
|
||
<h2><a name="alg" id="alg">How the server selects the proper name-based virtual host</a></h2>
|
||
|
||
<p>It is important to recognize that the first step in name-based virtual
|
||
host resolution is IP-based resolution. Name-based virtual host
|
||
resolution only chooses the most appropriate name-based virtual host
|
||
after narrowing down the candidates to the best IP-based match. Using a wildcard (*)
|
||
for the IP address in all of the VirtualHost directives makes this
|
||
IP-based mapping irrelevant.</p>
|
||
|
||
<p>When a request arrives, the server will find the best (most specific) matching
|
||
<code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> argument based on
|
||
the IP address and port used by the request. If there is more than one virtual host
|
||
containing this best-match address and port combination, Apache will further
|
||
compare the <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> and <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> directives to the server name
|
||
present in the request.</p>
|
||
|
||
<h3><a name="defaultvhost" id="defaultvhost">The default name-based vhost for an IP and port combination </a></h3>
|
||
<p> If no matching ServerName or ServerAlias is found in the set of
|
||
virtual hosts containing the most specific matching IP address and port
|
||
combination, then <strong>the first listed virtual host</strong> that
|
||
matches that will be used.</p>
|
||
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
|
||
<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#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>The first step is to create a <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> block for
|
||
each different host that you would like to serve. Inside each <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> block, you will need at minimum a
|
||
<code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> directive to designate
|
||
which host is served and a <code class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>
|
||
directive to show where in the filesystem the content for that host
|
||
lives.</p>
|
||
|
||
<div class="note"><h3>Main host goes away</h3>
|
||
<p> Any request that doesn't match an existing <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> is handled by the global
|
||
server configuration, regardless of the hostname or ServerName.</p>
|
||
|
||
<p> When you add a name-based virtual host to an existing server, and
|
||
the virtual host arguments match preexisting IP and port combinations,
|
||
requests will now be handled by an explicit virtual host. In this case,
|
||
it's usually wise to create a <a href="#defaultvhost">default virtual host</a>
|
||
with a <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> matching that of
|
||
the base server. New domains on the same interface and port, but
|
||
requiring separate configurations, can then be added as subsequent (non-default)
|
||
virtual hosts.</p>
|
||
</div>
|
||
|
||
<p>For example, suppose that you are serving the domain
|
||
<code>www.example.com</code> and you wish to add the virtual host
|
||
<code>other.example.com</code>, which points at the same IP address.
|
||
Then you simply add the following to <code>httpd.conf</code>:</p>
|
||
|
||
<div class="example"><p><code>
|
||
<VirtualHost *:80><br />
|
||
<span class="indent">
|
||
# This first-listed virtual host is also the default for *:80
|
||
ServerName www.example.com<br />
|
||
ServerAlias example.com *.example.com<br />
|
||
DocumentRoot /www/domain<br />
|
||
</span>
|
||
</VirtualHost><br />
|
||
<br />
|
||
<VirtualHost *:80><br />
|
||
<span class="indent">ServerName other.example.com<br />
|
||
DocumentRoot /www/otherdomain<br />
|
||
</span>
|
||
</VirtualHost><br />
|
||
</code></p></div>
|
||
|
||
<p>You can alternatively specify an explicit IP address in place of the
|
||
<code>*</code> in <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> directives. For example, you might want to do this
|
||
in order to run some name-based virtual hosts on one IP address, and either
|
||
IP-based, or another set of name-based virtual hosts on another address.</p>
|
||
|
||
<p>Many servers want to be accessible by more than one name. This is
|
||
possible with the <code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code>
|
||
directive, placed inside the <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> section. For example in the first <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code> block above, the
|
||
<code class="directive"><a href="../mod/core.html#serveralias">ServerAlias</a></code> directive indicates that
|
||
the listed names are other names which people can use to see that same
|
||
web site:</p>
|
||
|
||
<div class="example"><p><code>
|
||
ServerAlias example.com *.example.com
|
||
</code></p></div>
|
||
|
||
<p>then requests for all hosts in the <code>example.com</code> domain will
|
||
be served by the <code>www.example.com</code> virtual host. The wildcard
|
||
characters <code>*</code> and <code>?</code> can be used to match names.
|
||
Of course, you can't just make up names and place them in <code class="directive"><a href="../mod/core.html#servername">ServerName</a></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 class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></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-dict.html#Context">Context</a> of the
|
||
directive. Configuration directives set in the <em>main server context</em>
|
||
(outside any <code class="directive"><a href="../mod/core.html#virtualhost"><VirtualHost></a></code>
|
||
container) will be used only if they are not overridden by the virtual host
|
||
settings.</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> |
|
||
<a href="../en/vhosts/name-based.html" title="English"> en </a> |
|
||
<a href="../fr/vhosts/name-based.html" hreflang="fr" rel="alternate" title="Fran<61>ais"> fr </a> |
|
||
<a href="../ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
|
||
<a href="../ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
|
||
<a href="../tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="T<>rk<72>e"> tr </a></p>
|
||
</div><div id="footer">
|
||
<p class="apache">Copyright 2011 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
|
||
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
|
||
</body></html> |