details.html.en revision 15107611640cec4e666dd7e2e1dee15c270e9e98
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess This file is generated from xml source: DO NOT EDIT
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
5a58787efeb02a1c3f06569d019ad81fd2efa06end<title>An In-Depth Discussion of Virtual Host Matching - Apache HTTP Server</title>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<link href="/style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
5a58787efeb02a1c3f06569d019ad81fd2efa06end<link href="/style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
5a58787efeb02a1c3f06569d019ad81fd2efa06end<link href="/style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
5a58787efeb02a1c3f06569d019ad81fd2efa06end<link href="/images/favicon.ico" rel="shortcut icon" /></head>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<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>
52fff662005b1866a3ff09bb6c902800c5cc6dedjerenkrantz<p class="apache">Apache HTTP Server Version 2.3</p>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<div class="up"><a href="./"><img title="<-" alt="<-" src="/images/left.gif" /></a></div>
4b5981e276e93df97c34e4da05ca5cf8bbd937dand<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>An In-Depth Discussion of Virtual Host Matching</h1>
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd<p><span>Available Languages: </span><a href="/en/vhosts/details.html" title="English"> en </a> |
d05d0eb4ae6d2a5e513fc3bf2555ce33da416634nd<a href="/fr/vhosts/details.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> |
4b3a8afbfcea8b265d179a122bf40dfedd1ce280takashi<a href="/ko/vhosts/details.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
4b3a8afbfcea8b265d179a122bf40dfedd1ce280takashi<a href="/tr/vhosts/details.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p>
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen <p>This document attempts to explain
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen exactly what Apache HTTP Server does when deciding what virtual host to
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen serve a request from.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If you just want to <cite>make it work</cite> without
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess understanding how, here are <a href="examples.html">some
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#configparsing">Configuration File Parsing</a></li>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#hostmatching">Virtual Host Matching</a></li>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#tips">Tips</a></li>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen<h2><a name="configparsing" id="configparsing">Configuration File Parsing</a></h2>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>There is a <em>main_server</em> which consists of all the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess definitions appearing outside of
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code><VirtualHost></code> sections. There are virtual
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess sections.</p>
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen <code class="directive"><a href="/mod/core.html#servername">ServerName</a></code> directive
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen may appear anywhere within the definition of a server. However,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess each appearance overrides the previous appearance (within that
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess server).</p>
1696993fbee984b093ae8b823e3ea3fa80eae486covener <p>The main_server has no default
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen <code>ServerAlias</code>. The default <code>ServerName</code>,
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen if not specified, is deduced from the server's IP address.</p>
1696993fbee984b093ae8b823e3ea3fa80eae486covener <p>Port numbers specified in the <code>VirtualHost</code> directive do
1696993fbee984b093ae8b823e3ea3fa80eae486covener not influence what port numbers Apache will listen on, they only discriminate between
1696993fbee984b093ae8b823e3ea3fa80eae486covener which <code>VirtualHost</code> will be selected to handle a request.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Each address appearing in the <code>VirtualHost</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess directive can have an optional port. If the port is unspecified
1696993fbee984b093ae8b823e3ea3fa80eae486covener it is treated as a wildcard port. The special port <code>*</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess indicates a wildcard that matches any port. Collectively the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess entire set of addresses (including multiple <code>A</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess record results from DNS lookups) are called the vhost's
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Unless a <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code>
1696993fbee984b093ae8b823e3ea3fa80eae486covener directive is used for the exact IP address and port pair in the
1696993fbee984b093ae8b823e3ea3fa80eae486covener <code>VirtualHost</code> directive, Apache selects the best match
1696993fbee984b093ae8b823e3ea3fa80eae486covener only on the basis of the IP address (or wildcard) and port number.
1696993fbee984b093ae8b823e3ea3fa80eae486covener If there are multiple identical best matches, the first <code>VirtualHost</code>
1696993fbee984b093ae8b823e3ea3fa80eae486covener appearing in the configuration file will be selected.</p>
1696993fbee984b093ae8b823e3ea3fa80eae486covener <p>If you want Apache to <em>further</em> discriminate on the basis of the
1696993fbee984b093ae8b823e3ea3fa80eae486covener HTTP <code>Host</code> header supplied by the client, the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>NameVirtualHost</code> directive <em>must</em> appear
1696993fbee984b093ae8b823e3ea3fa80eae486covener with the exact IP address (or wildcard) and port pair used in a correspnding
1696993fbee984b093ae8b823e3ea3fa80eae486covener <p>The name-based virtual host selection occurs only after the a single IP-based
1696993fbee984b093ae8b823e3ea3fa80eae486covener virtual host has been selected, and only considers the set of virtual hosts
1696993fbee984b093ae8b823e3ea3fa80eae486covener the carry an identical IP address and port pair.</p>
1696993fbee984b093ae8b823e3ea3fa80eae486covener <p>Hostnames can be used in place of IP addresses in a virtual host definition,
1696993fbee984b093ae8b823e3ea3fa80eae486covener but it is resolved at startup and is not recommended.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Multiple <code>NameVirtualHost</code> directives can be used
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess each with a set of <code>VirtualHost</code> directives but only
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess one <code>NameVirtualHost</code> directive should be used for
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess each specific IP:port pair.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>VirtualHost</code> directives is not important which
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess makes the following two examples identical (only the order of
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess the <code>VirtualHost</code> directives for <em>one</em>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address set is important, see below):</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 111.22.33.44<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 111.22.33.44><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # server A<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 111.22.33.44><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # server B<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 111.22.33.55<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 111.22.33.55><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # server C<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 111.22.33.55><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # server D<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 111.22.33.44><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # server A<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 111.22.33.55><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # server C<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 111.22.33.44><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # server B<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 111.22.33.55><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # server D<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 111.22.33.44<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 111.22.33.55<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>(To aid the readability of your configuration you should
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess prefer the left variant.)</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>During initialization a list for each IP address is
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess generated and inserted into an hash table. If the IP address is
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess used in a <code>NameVirtualHost</code> directive the list
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess contains all name-based vhosts for the given IP address. If
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess there are no vhosts defined for that address the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>NameVirtualHost</code> directive is ignored and an error
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess is logged. For an IP-based vhost the list in the hash table is
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess empty.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Due to a fast hashing function the overhead of hashing an IP
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address during a request is minimal and almost not existent.
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Additionally the table is optimized for IP addresses which vary
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess in the last octet.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>For every vhost various default values are set. In
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess particular:</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>If a vhost has no <code class="directive"><a href="/mod/core.html#serveradmin">ServerAdmin</a></code>,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code class="directive"><a href="/mod/core.html#resourceconfig">ResourceConfig</a></code>,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code class="directive"><a href="/mod/core.html#accessconfig">AccessConfig</a></code>,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code class="directive"><a href="/mod/core.html#timeout">Timeout</a></code>,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code class="directive"><a href="/mod/core.html#keepalivetimeout">KeepAliveTimeout</a></code>,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code class="directive"><a href="/mod/core.html#keepalive">KeepAlive</a></code>,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code class="directive"><a href="/mod/core.html#maxkeepaliverequests">MaxKeepAliveRequests</a></code>,
2bc7f1cf720973a67f8ff7a8d523e40569ae5b6cnd <code class="directive"><a href="/mod/core.html#receivebuffersize">ReceiveBufferSize</a></code>,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess or <code class="directive"><a href="/mod/core.html#sendbuffersize">SendBufferSize</a></code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess directive then the respective value is inherited from the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess main_server. (That is, inherited from whatever the final
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess setting of that value is in the main_server.)</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>The "lookup defaults" that define the default directory
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess permissions for a vhost are merged with those of the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess main_server. This includes any per-directory configuration
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess information for any module.</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>The per-server configs for each module from the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess main_server are merged into the vhost server.</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Essentially, the main_server is treated as "defaults" or a
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess "base" on which to build each vhost. But the positioning of
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess these main_server definitions in the config file is largely
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess irrelevant -- the entire config of the main_server has been
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess parsed when this final merging occurs. So even if a main_server
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess definition appears after a vhost definition it might affect the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhost definition.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If the main_server has no <code>ServerName</code> at this
9bcfc3697a91b5215893a7d0206865b13fc72148nd point, then the hostname of the machine that <code class="program"><a href="/programs/httpd.html">httpd</a></code>
9bcfc3697a91b5215893a7d0206865b13fc72148nd is running on is used instead. We will call the <em>main_server address
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess set</em> those IP addresses returned by a DNS lookup on the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess name-based vhost defaults to the address given first in the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>VirtualHost</code> statement defining the vhost.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Any vhost that includes the magic <code>_default_</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess wildcard is given the same <code>ServerName</code> as the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess main_server.</p>
5a58787efeb02a1c3f06569d019ad81fd2efa06end</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="hostmatching" id="hostmatching">Virtual Host Matching</a></h2>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The server determines which vhost to use for a request as
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess follows:</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <h3><a name="hashtable" id="hashtable">Hash table lookup</a></h3>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>When the connection is first made by a client, the IP
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address to which the client connected is looked up in the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess internal IP hash table.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If the lookup fails (the IP address wasn't found) the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess request is served from the <code>_default_</code> vhost if
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess there is such a vhost for the port to which the client sent the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess request. If there is no matching <code>_default_</code> vhost
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess the request is served from the main_server.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If the IP address is not found in the hash table then the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess match against the port number may also result in an entry
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess corresponding to a <code>NameVirtualHost *</code>, which is
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess subsequently handled like other name-based vhosts.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If the lookup succeeded (a corresponding list for the IP
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address was found) the next step is to decide if we have to
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess deal with an IP-based or a name-base vhost.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <h3><a name="ipbased" id="ipbased">IP-based vhost</a></h3>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If the entry we found has an empty name list then we have
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess found an IP-based vhost, no further actions are performed and
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess the request is served from that vhost.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <h3><a name="namebased" id="namebased">Name-based vhost</a></h3>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If the entry corresponds to a name-based vhost the name list
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess contains one or more vhost structures. This list contains the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhosts in the same order as the <code>VirtualHost</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess directives appear in the config file.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The first vhost on this list (the first vhost in the config
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess file with the specified IP address) has the highest priority
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess and catches any request to an unknown server name or a request
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If the client provided a <code>Host:</code> header field the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess list is searched for a matching vhost and the first hit on a
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>ServerName</code> or <code>ServerAlias</code> is taken
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess and the request is served from that vhost. A <code>Host:</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess header field can contain a port number, but Apache always
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess matches against the real port to which the client sent the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess request.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>Host:</code> header field we don't know to what server
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen the client tried to connect to. In this case, the first virtual host
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen (that is, the one listed first in the server configuration file) for
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen the IP address and port to which the client connected, is
15107611640cec4e666dd7e2e1dee15c270e9e98rbowen used to serve this request.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <h3><a name="persistent" id="persistent">Persistent connections</a></h3>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The IP lookup described above is only done <em>once</em> for a
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess particular TCP/IP session while the name lookup is done on
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess connection. In other words a client may request pages from
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess different name-based vhosts during a single persistent
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess connection.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <h3><a name="absoluteURI" id="absoluteURI">Absolute URI</a></h3>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>If the URI from the request is an absolute URI, and its
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess hostname and port match the main server or one of the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess configured virtual hosts <em>and</em> match the address and
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess port to which the client sent the request, then the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess scheme/hostname/port prefix is stripped off and the remaining
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess relative URI is served by the corresponding main server or
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess virtual host. If it does not match, then the URI remains
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess untouched and the request is taken to be a proxy request.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess<h3><a name="observations" id="observations">Observations</a></h3>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>A name-based vhost can never interfere with an IP-base
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhost and vice versa. IP-based vhosts can only be reached
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess through an IP address of its own address set and never
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess through any other address. The same applies to name-based
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhosts, they can only be reached through an IP address of the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess corresponding address set which must be defined with a
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess checks are never performed for an IP-based vhost.</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>The order of name-/IP-based, the <code>_default_</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhost and the <code>NameVirtualHost</code> directive within
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess the config file is not important. Only the ordering of
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess name-based vhosts for a specific address set is significant.
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess The one name-based vhosts that comes first in the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess configuration file has the highest priority for its
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess corresponding address set.</li>
1696993fbee984b093ae8b823e3ea3fa80eae486covener <li>The <code>Host:</code> header field is never used during the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess matching process. Apache always uses the real port to which
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess the client sent the request.</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>If two IP-based vhosts have an address in common, the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhost appearing first in the config file is always matched.
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Such a thing might happen inadvertently. The server will give
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess a warning in the error logfile when it detects this.</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>A <code>_default_</code> vhost catches a request only if
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess there is no other vhost with a matching IP address
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <em>and</em> a matching port number for the request. The
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess request is only caught if the port number to which the client
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess sent the request matches the port number of your
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess specified (<em>i.e.</em>, <code>_default_:*</code>) to catch
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess requests to any available port. This also applies to
1696993fbee984b093ae8b823e3ea3fa80eae486covener <code>NameVirtualHost *</code> vhosts. Note that this is simply an
1696993fbee984b093ae8b823e3ea3fa80eae486covener extension of the "best match" principle, as a specific and exact match
1696993fbee984b093ae8b823e3ea3fa80eae486covener is favored over a wildcard.</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>The main_server is only used to serve a request if the IP
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address and port number to which the client connected is
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess unspecified and does not match any other vhost (including a
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>_default_</code> vhost). In other words the main_server
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess combination (unless there is a <code>_default_</code> vhost
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess which matches that port).</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>A <code>_default_</code> vhost or the main_server is
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <em>never</em> matched for a request with an unknown or
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess connected to an address (and port) which is used for
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>You should never specify DNS names in
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>VirtualHost</code> directives because it will force
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess your server to rely on DNS to boot. Furthermore it poses a
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess security threat if you do not control the DNS for all the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess domains listed. There's <a href="/dns-caveats.html">more
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess information</a> available on this and the next two
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess topics.</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li><code>ServerName</code> should always be set for each
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhost. Otherwise A DNS lookup is required for each
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhost.</li>
5a58787efeb02a1c3f06569d019ad81fd2efa06end</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>In addition to the tips on the <a href="/dns-caveats.html#tips">DNS Issues</a> page, here are
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess some further tips:</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>Place all main_server definitions before any
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>VirtualHost</code> definitions. (This is to aid the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess readability of the configuration -- the post-config merging
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess process makes it non-obvious that definitions mixed in around
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess virtual hosts might affect all virtual hosts.)</li>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <li>Group corresponding <code>NameVirtualHost</code> and
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>VirtualHost</code> definitions in your configuration to
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess ensure better readability.</li>
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd<p><span>Available Languages: </span><a href="/en/vhosts/details.html" title="English"> en </a> |
d05d0eb4ae6d2a5e513fc3bf2555ce33da416634nd<a href="/fr/vhosts/details.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> |
4b3a8afbfcea8b265d179a122bf40dfedd1ce280takashi<a href="/ko/vhosts/details.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
4b3a8afbfcea8b265d179a122bf40dfedd1ce280takashi<a href="/tr/vhosts/details.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p>
50039065d571fe01fd458a3f031c995a1fd53c22rbowen<p class="apache">Copyright 2010 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>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<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>