examples.html.en revision 4b5981e276e93df97c34e4da05ca5cf8bbd937da
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<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>VirtualHost Examples</h1>
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd<p><span>Available Languages: </span><a href="/en/vhosts/examples.html" title="English"> en </a> |
d05d0eb4ae6d2a5e513fc3bf2555ce33da416634nd<a href="/fr/vhosts/examples.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> |
c7811a175dc15d2172cc95f1c9791bbb6caf9b04nd<a href="/ja/vhosts/examples.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd<a href="/ko/vhosts/examples.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>This document attempts to answer the commonly-asked questions about
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess setting up virtual hosts. These scenarios are those involving multiple
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen web sites running on a single server, via <a href="name-based.html">name-based</a> or <a href="ip-based.html">IP-based</a> virtual hosts.
5a58787efeb02a1c3f06569d019ad81fd2efa06end<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#purename">Running several name-based web
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#twoips">Name-based hosts on more than one
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#intraextra">Serving the same content on
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess different IP addresses (such as an internal and external
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#port">Running different sites on different
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#ip">IP-based virtual hosting</a></li>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#ipport">Mixed port-based and ip-based virtual
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#mixed">Mixed name-based and IP-based
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen<li><img alt="" src="/images/down.gif" /> <a href="#proxy">Using <code>Virtual_host</code> and
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#default">Using <code>_default_</code>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#migrate">Migrating a name-based vhost to an
5a58787efeb02a1c3f06569d019ad81fd2efa06end<li><img alt="" src="/images/down.gif" /> <a href="#serverpath">Using the <code>ServerPath</code>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="purename" id="purename">Running several name-based web
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Your server has a single IP address, and multiple aliases (CNAMES)
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess point to this machine in DNS. You want to run a web server for
261c62b53a9c707c64c7824eed68b5463bd23e62nd <code>www.example.com</code> and <code>www.example.org</code> on this
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess machine.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess host configurations on your Apache server does not magically
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess cause DNS entries to be created for those host names. You
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <em>must</em> have the names in DNS, resolving to your IP
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address, or nobody else will be able to see your web site. You
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess can put entries in your <code>hosts</code> file for local
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess testing, but that will work only from the machine with those
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess hosts entries.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # Ensure that Apache listens on port 80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # Listen for virtual host requests on all IP addresses<br />
dcf73e82ff6eda04fc24e50753631fd83bf61f3drbowen NameVirtualHost *:80<br />
dcf73e82ff6eda04fc24e50753631fd83bf61f3drbowen <VirtualHost *:80><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # Other directives here<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
dcf73e82ff6eda04fc24e50753631fd83bf61f3drbowen <VirtualHost *:80><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # Other directives here<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The asterisks match all addresses, so the main server serves no
261c62b53a9c707c64c7824eed68b5463bd23e62nd requests. Due to the fact that <code>www.example.com</code> is first
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess in the configuration file, it has the highest priority and can be seen
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess as the <cite>default</cite> or <cite>primary</cite> server. That means
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess that if a request is received that does not match one of the specified
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>ServerName</code> directives, it will be served by this first
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>You can, if you wish, replace <code>*</code> with the actual
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess IP address of the system. In that case, the argument to
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>VirtualHost</code> <em>must</em> match the argument to
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 172.20.30.40<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>However, it is additionally useful to use <code>*</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess on systems where the IP address is not predictable - for
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess example if you have a dynamic IP address with your ISP, and
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess you are using some variety of dynamic DNS solution. Since
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>*</code> matches any IP address, this configuration
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess would work without changes whenever your IP address
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess changes.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The above configuration is what you will want to use in almost
fd98d2e18dca5790daa7e49b4384937e6ba7666cerikabele all name-based virtual hosting situations. The only thing that this
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess configuration will not work for, in fact, is when you are serving
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess different content based on differing IP addresses or ports.</p>
5a58787efeb02a1c3f06569d019ad81fd2efa06end </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="twoips" id="twoips">Name-based hosts on more than one
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess techniques discussed here can be extended to any number of IP
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess addresses.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The server has two IP addresses. On one (<code>172.20.30.40</code>), we
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess will serve the "main" server, <code>server.domain.com</code> and on the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess other (<code>172.20.30.50</code>), we will serve two or more virtual hosts.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # This is the "main" server running on 172.20.30.40<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # This is the other address<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 172.20.30.50<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.50><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # Other directives here ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.50><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # Other directives here ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Any request to an address other than <code>172.20.30.50</code> will be
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess served from the main server. A request to <code>172.20.30.50</code> with an
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess unknown hostname, or no <code>Host:</code> header, will be served from
5a58787efeb02a1c3f06569d019ad81fd2efa06end </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="intraextra" id="intraextra">Serving the same content on
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess different IP addresses (such as an internal and external
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The server machine has two IP addresses (<code>192.168.1.1</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess and <code>172.20.30.40</code>). The machine is sitting between an
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess internal (intranet) network and an external (internet) network. Outside
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess of the network, the name <code>server.example.com</code> resolves to
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess the external address (<code>172.20.30.40</code>), but inside the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess network, that same name resolves to the internal address
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The server can be made to respond to internal and external requests
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess with the same content, with just one <code>VirtualHost</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess section.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 192.168.1.1<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 172.20.30.40<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 192.168.1.1 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess ServerAlias server<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Now requests from both networks will be served from the same
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess network, one can just use the name <code>server</code> rather
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess than the fully qualified host name
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Note also that, in the above example, you can replace the list
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess of IP addresses with <code>*</code>, which will cause the server to
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess respond the same on all addresses.</p>
5a58787efeb02a1c3f06569d019ad81fd2efa06end </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="port" id="port">Running different sites on different
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>You have multiple domains going to the same IP and also want to
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess serve multiple ports. By defining the ports in the "NameVirtualHost"
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess tag, you can allow this to work. If you try using <VirtualHost
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess name:port> without the NameVirtualHost name:port or you try to use
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess the Listen directive, your configuration will not work.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 8080<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 172.20.30.40:80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 172.20.30.40:8080<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40:80><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40:8080><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40:80><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40:8080><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
5a58787efeb02a1c3f06569d019ad81fd2efa06end </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="ip" id="ip">IP-based virtual hosting</a></h2>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The server has two IP addresses (<code>172.20.30.40</code> and
261c62b53a9c707c64c7824eed68b5463bd23e62nd <code>www.example.com</code> and <code>www.example.org</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess respectively.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.50><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Requests for any address not specified in one of the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>localhost</code>, for example) will go to the main server, if
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess there is one.</p>
5a58787efeb02a1c3f06569d019ad81fd2efa06end </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="ipport" id="ipport">Mixed port-based and ip-based virtual
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The server machine has two IP addresses (<code>172.20.30.40</code> and
261c62b53a9c707c64c7824eed68b5463bd23e62nd <code>www.example.com</code> and <code>www.example.org</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess respectively. In each case, we want to run hosts on ports 80 and
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 172.20.30.40:80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 172.20.30.40:8080<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 172.20.30.50:80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 172.20.30.50:8080<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40:80><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40:8080><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.50:80><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.50:8080><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
5a58787efeb02a1c3f06569d019ad81fd2efa06end </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="mixed" id="mixed">Mixed name-based and IP-based
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>On some of my addresses, I want to do name-based virtual hosts, and
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess on others, IP-based hosts.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 172.20.30.40<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # IP-based<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.50><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.60><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
5a58787efeb02a1c3f06569d019ad81fd2efa06end </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen<h2><a name="proxy" id="proxy">Using <code>Virtual_host</code> and
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen <p>The following example allows a front-end machine to proxy a
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen virtual host through to a server running on another machine. In the
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen example, a virtual host of the same name is configured on a machine
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen at <code>192.168.111.2</code>. The <code class="directive"><a href="/mod/mod_proxy.html#proxypreservehost on">ProxyPreserveHost On</a></code> directive is
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen used so that the desired hostname is passed through, in case we are
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen proxying multiple hostnames to a single machine.</p>
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen <VirtualHost *:*><br />
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen ProxyPreserveHost On<br />
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen </VirtualHost>
f8dee27891059abb09ff5ca3fc5434f5719d22a0rbowen </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="default" id="default">Using <code>_default_</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <h3><a name="defaultallports" id="defaultallports"><code>_default_</code> vhosts
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Catching <em>every</em> request to any unspecified IP address and
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess port, <em>i.e.</em>, an address/port combination that is not used for
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess any other virtual host.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost _default_:*><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Using such a default vhost with a wildcard port effectively prevents
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess any request going to the main server.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>A default vhost never serves a request that was sent to an
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address/port that is used for name-based vhosts. If the request
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess contained an unknown or no <code>Host:</code> header it is always
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess served from the primary name-based vhost (the vhost for that
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address/port appearing first in the configuration file).</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>You can use <code class="directive"><a href="/mod/mod_alias.html#aliasmatch">AliasMatch</a></code> or
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code class="directive"><a href="/mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> to rewrite any
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess request to a single information page (or script).</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <h3><a name="defaultdifferentports" id="defaultdifferentports"><code>_default_</code> vhosts
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Same as setup 1, but the server listens on several ports and we want
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess to use a second <code>_default_</code> vhost for port 80.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost _default_:80><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost _default_:*><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The default vhost for port 80 (which <em>must</em> appear before any
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess default vhost with a wildcard port) catches all requests that were sent
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess to an unspecified IP address. The main server is never used to serve a
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess request.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <h3><a name="defaultoneport" id="defaultoneport"><code>_default_</code> vhosts
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>We want to have a default vhost for port 80, but no other default
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhosts.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost _default_:80><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>A request to an unspecified address on port 80 is served from the
d5b8072762cf428c4c703ed7054ae948d41c910bnd default vhost. Any other request to an unspecified address and port is
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess served from the 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="migrate" id="migrate">Migrating a name-based vhost to an
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The name-based vhost with the hostname
261c62b53a9c707c64c7824eed68b5463bd23e62nd <code>www.example.org</code> (from our <a href="#name">name-based</a> example, setup 2) should get its own IP
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess address. To avoid problems with name servers or proxies who cached the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess old IP address for the name-based vhost we want to provide both
a795ca2487c774aa6fe75c765a2bf17f969f7af7nd variants during a migration phase.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess The solution is easy, because we can simply add the new IP address
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess (<code>172.20.30.50</code>) to the <code>VirtualHost</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess directive.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess Listen 80<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 172.20.30.40<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40 172.20.30.50><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>The vhost can now be accessed through the new address (as an
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess IP-based vhost) and through the old address (as a name-based
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess vhost).</p>
5a58787efeb02a1c3f06569d019ad81fd2efa06end </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
5a58787efeb02a1c3f06569d019ad81fd2efa06end<h2><a name="serverpath" id="serverpath">Using the <code>ServerPath</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>We have a server with two name-based vhosts. In order to match the
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess correct virtual host a client must send the correct <code>Host:</code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess header. Old HTTP/1.0 clients do not send such a header and Apache has
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess no clue what vhost the client tried to reach (and serves the request
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess from the primary vhost). To provide as much backward compatibility as
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess possible we create a primary vhost which returns a single page
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess containing links with an URL prefix to the name-based virtual
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess hosts.</p>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <div class="example"><h3>Server configuration</h3><p><code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess NameVirtualHost 172.20.30.40<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # primary vhost<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess RewriteEngine On<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess ServerPath /sub1/<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess RewriteEngine On<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <VirtualHost 172.20.30.40><br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess ServerPath /sub2/<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess RewriteEngine On<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess # ...<br />
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess </VirtualHost>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <p>Due to the <code class="directive"><a href="/mod/core.html#serverpath">ServerPath</a></code>
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess directive a request to the URL
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>http://www.sub1.domain.tld/sub1/</code> is <em>always</em> served
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess from the sub1-vhost.<br /> A request to the URL
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess served from the sub1-vhost if the client sent a correct
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>Host:</code> header. If no <code>Host:</code> header is sent the
a795ca2487c774aa6fe75c765a2bf17f969f7af7nd client gets the information page from the primary host.</p>
a795ca2487c774aa6fe75c765a2bf17f969f7af7nd <p>Please note that there is one oddity: A request to
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>http://www.sub2.domain.tld/sub1/</code> is also served from the
a795ca2487c774aa6fe75c765a2bf17f969f7af7nd sub1-vhost if the client sent no <code>Host:</code> header.</p>
a795ca2487c774aa6fe75c765a2bf17f969f7af7nd <p>The <code class="directive"><a href="/mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directives
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess are used to make sure that a client which sent a correct
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess <code>Host:</code> header can use both URL variants, <em>i.e.</em>,
fefb8b844b6286bfc41bb2e0c4cc003b8e7d4ff2kess with or without URL prefix.</p>
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd<p><span>Available Languages: </span><a href="/en/vhosts/examples.html" title="English"> en </a> |
d05d0eb4ae6d2a5e513fc3bf2555ce33da416634nd<a href="/fr/vhosts/examples.html" hreflang="fr" rel="alternate" title="Fran�ais"> fr </a> |
c7811a175dc15d2172cc95f1c9791bbb6caf9b04nd<a href="/ja/vhosts/examples.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
ad74a0524a06bfe11b7de9e3b4ce7233ab3bd3f7nd<a href="/ko/vhosts/examples.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
b95ae799514ad86a15610ad75808d7065e9847c9kess<p class="apache">Copyright 1995-2005 The Apache Software Foundation or its licensors, as applicable.<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>