1<?xml version="1.0" encoding="ISO-8859-1"?> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 3<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- 4 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 5 This file is generated from xml source: DO NOT EDIT 6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 7 --> 8<title>Name-based Virtual Host Support - Apache HTTP Server</title> 9<link href="/style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /> 10<link href="/style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /> 11<link href="/style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="/style/css/prettify.css" /> 12<script src="/style/scripts/prettify.js" type="text/javascript"> 13</script> 14 15<link href="/images/favicon.ico" rel="shortcut icon" /></head> 16<body id="manual-page"><div id="page-header"> 17<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p> 18<p class="apache">Apache HTTP Server Version 2.2</p> 19<img alt="" src="/images/feather.gif" /></div> 20<div class="up"><a href="./"><img title="<-" alt="<-" src="/images/left.gif" /></a></div> 21<div id="path"> 22<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.2</a> > <a href="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>Name-based Virtual Host Support</h1> 23<div class="toplang"> 24<p><span>Available Languages: </span><a href="/de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | 25<a href="/en/vhosts/name-based.html" title="English"> en </a> | 26<a href="/fr/vhosts/name-based.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> | 27<a href="/ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | 28<a href="/ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | 29<a href="/tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> 30</div> 31 32 <p>This document describes when and how to use name-based virtual hosts.</p> 33</div> 34<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> 35<li><img alt="" src="/images/down.gif" /> <a href="#using">Using Name-based Virtual Hosts</a></li> 36<li><img alt="" src="/images/down.gif" /> <a href="#compat">Compatibility with Older Browsers</a></li> 37</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><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div> 38<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 39<div class="section"> 40<h2><a name="namevip" id="namevip">Name-based vs. IP-based Virtual Hosts</a></h2> 41 42 <p>IP-based virtual hosts use the IP address of the connection to 43 determine the correct virtual host to serve. Therefore you need to 44 have a separate IP address for each host. With name-based virtual 45 hosting, the server relies on the client to report the hostname as 46 part of the HTTP headers. Using this technique, many different hosts 47 can share the same IP address.</p> 48 49 <p>Name-based virtual hosting is usually simpler, since you need 50 only configure your DNS server to map each hostname to the correct 51 IP address and then configure the Apache HTTP Server to recognize 52 the different hostnames. Name-based virtual hosting also eases 53 the demand for scarce IP addresses. Therefore you should use 54 name-based virtual hosting unless you are using equipment 55 that explicitly demands IP-based hosting. Historical reasons for 56 IP-based virtual hosting based on client support are no longer 57 applicable to a general-purpose web server, unless you are 58 using a <code class="module"><a href="/mod/mod_ssl.html">mod_ssl</a></code> version without SNI support 59 (standard in Apache releases since 2.2.12).</p> 60 61</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 62<div class="section"> 63<h2><a name="using" id="using">Using Name-based Virtual Hosts</a></h2> 64 65<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> 66 67 <p>To use name-based virtual hosting, you must designate the IP 68 address (and possibly port) on the server that will be accepting 69 requests for the hosts. This is configured using the <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive. 70 In the normal case where any and all IP addresses on the server should 71 be used, you can use <code>*</code> as the argument to <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code>. If you're planning to use 72 multiple ports (e.g. running SSL) you should add a Port to the argument, 73 such as <code>*:80</code>. Note that mentioning an IP address in a 74 <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive does not 75 automatically make the server listen to that IP address. See 76 <a href="/bind.html">Setting which addresses and ports Apache uses</a> 77 for more details. In addition, any IP address specified here must be 78 associated with a network interface on the server.</p> 79 80 <p>The next step is to create a <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> block for 81 each different host that you would like to serve. The argument to the 82 <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> directive 83 must match a defined <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code> directive. (In this usual case, 84 this will be "*:80"). Inside each <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> block, you will need at minimum a 85 <code class="directive"><a href="/mod/core.html#servername">ServerName</a></code> directive to designate 86 which host is served and a <code class="directive"><a href="/mod/core.html#documentroot">DocumentRoot</a></code> 87 directive to show where in the filesystem the content for that host 88 lives.</p> 89 90 <div class="note"><h3>Main host goes away</h3> 91 <p>If you are adding virtual hosts to an existing web server, you 92 must also create a <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> block for the existing host. The <code class="directive"><a href="/mod/core.html#servername">ServerName</a></code> and <code class="directive"><a href="/mod/core.html#documentroot">DocumentRoot</a></code> included in this virtual host should be the 93 same as the global <code class="directive"><a href="/mod/core.html#servername">ServerName</a></code> and 94 <code class="directive"><a href="/mod/core.html#documentroot">DocumentRoot</a></code>. List this virtual 95 host first in the configuration file so that it will act as the default 96 host.</p> 97 </div> 98 99 <p>For example, suppose that you are serving the domain 100 <code>www.domain.tld</code> and you wish to add the virtual host 101 <code>www.otherdomain.tld</code>, which points at the same IP address. 102 Then you simply add the following to <code>httpd.conf</code>:</p> 103 104 <div class="example"><p><code> 105 NameVirtualHost *:80<br /> 106 <br /> 107 <VirtualHost *:80><br /> 108 <span class="indent"> 109 ServerName www.domain.tld<br /> 110 ServerAlias domain.tld *.domain.tld<br /> 111 DocumentRoot /www/domain<br /> 112 </span> 113 </VirtualHost><br /> 114 <br /> 115 <VirtualHost *:80><br /> 116 <span class="indent">ServerName www.otherdomain.tld<br /> 117 DocumentRoot /www/otherdomain<br /> 118 </span> 119 </VirtualHost><br /> 120 </code></p></div> 121 122 <p>You can alternatively specify an explicit IP address in place of the 123 <code>*</code> in both the <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code> and <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> directives. For example, you might want to do this 124 in order to run some name-based virtual hosts on one IP address, and either 125 IP-based, or another set of name-based virtual hosts on another address.</p> 126 127 <p>Many servers want to be accessible by more than one name. This is 128 possible with the <code class="directive"><a href="/mod/core.html#serveralias">ServerAlias</a></code> 129 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 130 <code class="directive"><a href="/mod/core.html#serveralias">ServerAlias</a></code> directive indicates that 131 the listed names are other names which people can use to see that same 132 web site:</p> 133 134 <div class="example"><p><code> 135 ServerAlias domain.tld *.domain.tld 136 </code></p></div> 137 138 <p>then requests for all hosts in the <code>domain.tld</code> domain will 139 be served by the <code>www.domain.tld</code> virtual host. The wildcard 140 characters <code>*</code> and <code>?</code> can be used to match names. 141 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 142 first have your DNS server properly configured to map those names to an IP 143 address associated with your server.</p> 144 145 <p>The complete list of names in the <code class="directive"><a href="/mod/core.html#virtualhost">VirtualHost</a></code> directive are treated just like a (non wildcard) 146 <code class="directive"><a href="/mod/core.html#serveralias">ServerAlias</a></code>.</p> 147 148 <p>Finally, you can fine-tune the configuration of the virtual hosts 149 by placing other directives inside the <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> containers. Most directives can be 150 placed in these containers and will then change the configuration only of 151 the relevant virtual host. To find out if a particular directive is allowed, 152 check the <a href="/mod/directive-dict.html#Context">Context</a> of the 153 directive. Configuration directives set in the <em>main server context</em> 154 (outside any <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> 155 container) will be used only if they are not overridden by the virtual host 156 settings.</p> 157 158 <p>Now when a request arrives, the server will first check if it is using 159 an IP address that matches the <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code>. If it is, then it will look at each <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> section with a matching 160 IP address and try to find one where the <code class="directive"><a href="/mod/core.html#servername">ServerName</a></code> or <code>ServerAlias</code> matches the requested 161 hostname. If it finds one, then it uses the configuration for that server. 162 If no matching virtual host is found, then <strong>the first listed virtual 163 host</strong> that matches the IP address will be used.</p> 164 165 <p>As a consequence, the first listed virtual host is the <em>default</em> 166 virtual host. The <code class="directive"><a href="/mod/core.html#documentroot">DocumentRoot</a></code> from 167 the <em>main server</em> will <strong>never</strong> be used when an IP 168 address matches the <code class="directive"><a href="/mod/core.html#namevirtualhost">NameVirtualHost</a></code> 169 directive. If you would like to have a special configuration for requests 170 that do not match any particular virtual host, simply put that configuration 171 in a <code class="directive"><a href="/mod/core.html#virtualhost"><VirtualHost></a></code> 172 container and list it first in the configuration file.</p> 173 174</div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div> 175<div class="section"> 176<h2><a name="compat" id="compat">Compatibility with Older Browsers</a></h2> 177 178 <p>As mentioned earlier, there are some clients 179 who do not send the required data for the name-based virtual 180 hosts to work properly. These clients will always be sent the 181 pages from the first virtual host listed for that IP address 182 (the <cite>primary</cite> name-based virtual host).</p> 183 184 <div class="note"><h3>How much older?</h3> 185 <p>Please note that when we say older, we really do mean older. You are 186 very unlikely to encounter one of these browsers in use today. All 187 current versions of any browser send the <code>Host</code> header as 188 required for name-based virtual hosts.</p> 189 </div> 190 191 <p>There is a possible workaround with the <code class="directive"><a href="/mod/core.html#serverpath">ServerPath</a></code> 192 directive, albeit a slightly cumbersome one:</p> 193 194 <p>Example configuration:</p> 195 196 <div class="example"><p><code> 197 NameVirtualHost 111.22.33.44<br /> 198 <br /> 199 <VirtualHost 111.22.33.44><br /> 200 <span class="indent"> 201 ServerName www.domain.tld<br /> 202 ServerPath /domain<br /> 203 DocumentRoot /web/domain<br /> 204 </span> 205 </VirtualHost><br /> 206 </code></p></div> 207 208 <p>What does this mean? It means that a request for any URI 209 beginning with "<code>/domain</code>" will be served from the 210 virtual host <code>www.domain.tld</code>. This means that the 211 pages can be accessed as <code>http://www.domain.tld/domain/</code> 212 for all clients, although clients sending a <code>Host:</code> header 213 can also access it as <code>http://www.domain.tld/</code>.</p> 214 215 <p>In order to make this work, put a link on your primary 216 virtual host's page to 217 <code>http://www.domain.tld/domain/</code>. Then, in the virtual 218 host's pages, be sure to use either purely relative links 219 (<em>e.g.</em>, "<code>file.html</code>" or 220 "<code>/icons/image.gif</code>") or links containing the 221 prefacing <code>/domain/</code> (<em>e.g.</em>, 222 "<code>http://www.domain.tld/domain/misc/file.html</code>" or 223 "<code>/domain/misc/file.html</code>").</p> 224 225 <p>This requires a bit of discipline, but adherence to these 226 guidelines will, for the most part, ensure that your pages will 227 work with all browsers, new and old.</p> 228 229</div></div> 230<div class="bottomlang"> 231<p><span>Available Languages: </span><a href="/de/vhosts/name-based.html" hreflang="de" rel="alternate" title="Deutsch"> de </a> | 232<a href="/en/vhosts/name-based.html" title="English"> en </a> | 233<a href="/fr/vhosts/name-based.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> | 234<a href="/ja/vhosts/name-based.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> | 235<a href="/ko/vhosts/name-based.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> | 236<a href="/tr/vhosts/name-based.html" hreflang="tr" rel="alternate" title="T�rk�e"> tr </a></p> 237</div><div class="top"><a href="#page-header"><img src="/images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div> 238<script type="text/javascript"><!--//--><![CDATA[//><!-- 239var comments_shortname = 'httpd'; 240var comments_identifier = 'http://httpd.apache.org/docs/2.2/vhosts/name-based.html'; 241(function(w, d) { 242 if (w.location.hostname.toLowerCase() == "httpd.apache.org") { 243 d.write('<div id="comments_thread"><\/div>'); 244 var s = d.createElement('script'); 245 s.type = 'text/javascript'; 246 s.async = true; 247 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier; 248 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s); 249 } 250 else { 251 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>'); 252 } 253})(window, document); 254//--><!]]></script></div><div id="footer"> 255<p class="apache">Copyright 2013 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> 256<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!-- 257if (typeof(prettyPrint) !== 'undefined') { 258 prettyPrint(); 259} 260//--><!]]></script> 261</body></html>
