examples.html.en revision 3b3b7fc78d1f5bfc2769903375050048ff41ff26
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor This file is generated from xml source: DO NOT EDIT
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<title>VirtualHost Examples - Apache HTTP Server</title>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<link href="/style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<link href="/style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<link href="/style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<link href="/images/favicon.ico" rel="shortcut icon" /></head>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<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>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<div class="up"><a href="./"><img title="<-" alt="<-" src="/images/left.gif" /></a></div>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs-project/">Documentation</a> > <a href="../">Version 2.1</a> > <a href="./">Virtual Hosts</a></div><div id="page-content"><div id="preamble"><h1>VirtualHost Examples</h1>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<p><span>Available Languages: </span><a href="/en/vhosts/examples.html"> en </a></p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>This document attempts to answer the commonly-asked questions about
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor setting up virtual hosts. These scenarios are those involving multiple
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor 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. A document should be
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor coming soon about running sites on several servers behind a single
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor proxy server.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#purename">Running several name-based web
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<li><img alt="" src="/images/down.gif" /> <a href="#twoips">Name-based hosts on more than one
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<li><img alt="" src="/images/down.gif" /> <a href="#intraextra">Serving the same content on
c867dba1041640ecec7c8194d35a5b4ffce442earbowen different IP addresses (such as an internal and external
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<li><img alt="" src="/images/down.gif" /> <a href="#port">Running different sites on different
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<li><img alt="" src="/images/down.gif" /> <a href="#ip">IP-based virtual hosting</a></li>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<li><img alt="" src="/images/down.gif" /> <a href="#ipport">Mixed port-based and ip-based virtual
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<li><img alt="" src="/images/down.gif" /> <a href="#mixed">Mixed name-based and IP-based
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<li><img alt="" src="/images/down.gif" /> <a href="#default">Using <code>_default_</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<li><img alt="" src="/images/down.gif" /> <a href="#migrate">Migrating a name-based vhost to an
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<li><img alt="" src="/images/down.gif" /> <a href="#serverpath">Using the <code>ServerPath</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<h2><a name="purename" id="purename">Running several name-based web
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>Your server has a single IP address, and multiple aliases (CNAMES)
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor point to this machine in DNS. You want to run a web server for
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <code>www.example1.com</code> and <code>www.example2.org</code> on this
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor machine.</p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor host configurations on your Apache server does not magically
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor cause DNS entries to be created for those host names. You
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <em>must</em> have the names in DNS, resolving to your IP
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor address, or nobody else will be able to see your web site. You
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor can put entries in your <code>hosts</code> file for local
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor testing, but that will work only from the machine with those
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor hosts entries.</p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <div class="example"><h3>Server configuration</h3><p><code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # Ensure that Apache listens on port 80<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen Listen 80<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # Listen for virtual host requests on all IP addresses<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen NameVirtualHost *<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost *><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # Other directives here<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost *><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # Other directives here<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>The asterisks match all addresses, so the main server serves no
c867dba1041640ecec7c8194d35a5b4ffce442earbowen requests. Due to the fact that <code>www.example1.com</code> is first
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor in the configuration file, it has the highest priority and can be seen
c867dba1041640ecec7c8194d35a5b4ffce442earbowen as the <cite>default</cite> or <cite>primary</cite> server. That means
c867dba1041640ecec7c8194d35a5b4ffce442earbowen that if a request is received that does not match one of the specified
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code>ServerName</code> directives, it will be served by this first
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>You can, if you wish, replace <code>*</code> with the actual
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor IP address of the system. In that case, the argument to
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <code>VirtualHost</code> <em>must</em> match the argument to
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor NameVirtualHost 172.20.30.40<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.40><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>However, it is additionally useful to use <code>*</code>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor on systems where the IP address is not predictable - for
c867dba1041640ecec7c8194d35a5b4ffce442earbowen example if you have a dynamic IP address with your ISP, and
c867dba1041640ecec7c8194d35a5b4ffce442earbowen you are using some variety of dynamic DNS solution. Since
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic <code>*</code> matches any IP address, this configuration
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic would work without changes whenever your IP address
c867dba1041640ecec7c8194d35a5b4ffce442earbowen changes.</p>
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic <p>The above configuration is what you will want to use in almost
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic all name-based virtual hosting situations. The only think that this
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic configuration will not work for, in fact, is when you are serving
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic different content based on differing IP addresses or ports.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<h2><a name="twoips" id="twoips">Name-based hosts on more than one
c867dba1041640ecec7c8194d35a5b4ffce442earbowen techniques discussed here can be extended to any number of IP
c867dba1041640ecec7c8194d35a5b4ffce442earbowen addresses.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>The server has two IP addresses. On one (<code>172.20.30.40</code>), we
c867dba1041640ecec7c8194d35a5b4ffce442earbowen will serve the "main" server, <code>server.domain.com</code> and on the
c867dba1041640ecec7c8194d35a5b4ffce442earbowen other (<code>172.20.30.50</code>), we will serve two or more virtual hosts.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <div class="example"><h3>Server configuration</h3><p><code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen Listen 80<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor # This is the "main" server running on 172.20.30.40<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # This is the other address<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor NameVirtualHost 172.20.30.50<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.50><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor # Other directives here ...<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.50><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # Other directives here ...<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>Any request to an address other than <code>172.20.30.50</code> will be
c867dba1041640ecec7c8194d35a5b4ffce442earbowen served from the main server. A request to <code>172.20.30.50</code> with an
c867dba1041640ecec7c8194d35a5b4ffce442earbowen unknown hostname, or no <code>Host:</code> header, will be served from
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<h2><a name="intraextra" id="intraextra">Serving the same content on
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor different IP addresses (such as an internal and external
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>The server machine has two IP addresses (<code>192.168.1.1</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen and <code>172.20.30.40</code>). The machine is sitting between an
c867dba1041640ecec7c8194d35a5b4ffce442earbowen internal (intranet) network and an external (internet) network. Outside
c867dba1041640ecec7c8194d35a5b4ffce442earbowen of the network, the name <code>server.example.com</code> resolves to
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor the external address (<code>172.20.30.40</code>), but inside the
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor network, that same name resolves to the internal address
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>The server can be made to respond to internal and external requests
c867dba1041640ecec7c8194d35a5b4ffce442earbowen with the same content, with just one <code>VirtualHost</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen section.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <div class="example"><h3>Server configuration</h3><p><code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen NameVirtualHost 192.168.1.1<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen NameVirtualHost 172.20.30.40<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 192.168.1.1 172.20.30.40><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen ServerAlias server<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>Now requests from both networks will be served from the same
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor network, one can just use the name <code>server</code> rather
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor than the fully qualified host name
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>Note also that, in the above example, you can replace the list
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor of IP addresses with <code>*</code>, which will cause the server to
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor respond the same on all addresses.</p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<h2><a name="port" id="port">Running different sites on different
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>You have multiple domains going to the same IP and also want to
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor serve multiple ports. By defining the ports in the "NameVirtualHost"
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor tag, you can allow this to work. If you try using <VirtualHost
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor name:port> without the NameVirtualHost name:port or you try to use
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor the Listen directive, your configuration will not work.</p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <div class="example"><h3>Server configuration</h3><p><code>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor Listen 80<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor Listen 8080<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor NameVirtualHost 172.20.30.40:80<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor NameVirtualHost 172.20.30.40:8080<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.40:80><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.40:8080><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.40:80><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.40:8080><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<h2><a name="ip" id="ip">IP-based virtual hosting</a></h2>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>The server has two IP addresses (<code>172.20.30.40</code> and
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code>172.20.30.50</code>) which resolve to the names
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code>www.example1.com</code> and <code>www.example2.org</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen respectively.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <div class="example"><h3>Server configuration</h3><p><code>
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic Listen 80<br />
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic <VirtualHost 172.20.30.40><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.50><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>Requests for any address not specified in one of the
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code>localhost</code>, for example) will go to the main server, if
c867dba1041640ecec7c8194d35a5b4ffce442earbowen there is one.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<h2><a name="ipport" id="ipport">Mixed port-based and ip-based virtual
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>The server machine has two IP addresses (<code>172.20.30.40</code> and
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <code>172.20.30.50</code>) which resolve to the names
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <code>www.example1.com</code> and <code>www.example2.org</code>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor respectively. In each case, we want to run hosts on ports 80 and
53cf0034f617fdca55a345580e13afd88000e9ccjim <div class="example"><h3>Server configuration</h3><p><code>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor Listen 172.20.30.40:80<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor Listen 172.20.30.40:8080<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor Listen 172.20.30.50:80<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor Listen 172.20.30.50:8080<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.40:80><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.40:8080><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.50:80><br />
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic </VirtualHost><br />
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic <VirtualHost 172.20.30.50:8080><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost>
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
8e9c6d6438af1ccb46adaa60d34caa3ac98f3851igalic<h2><a name="mixed" id="mixed">Mixed name-based and IP-based
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>On some of my addresses, I want to do name-based virtual hosts, and
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor on others, IP-based hosts.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <div class="example"><h3>Server configuration</h3><p><code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen Listen 80<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen NameVirtualHost 172.20.30.40<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.40><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.40><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.40><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # IP-based<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.50><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.60><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<h2><a name="default" id="default">Using <code>_default_</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <h3><a name="defaultallports" id="defaultallports"><code>_default_</code> vhosts
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>Catching <em>every</em> request to any unspecified IP address and
c867dba1041640ecec7c8194d35a5b4ffce442earbowen port, <em>i.e.</em>, an address/port combination that is not used for
c867dba1041640ecec7c8194d35a5b4ffce442earbowen any other virtual host.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <div class="example"><h3>Server configuration</h3><p><code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost _default_:*><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>Using such a default vhost with a wildcard port effectively prevents
c867dba1041640ecec7c8194d35a5b4ffce442earbowen any request going to the main server.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>A default vhost never serves a request that was sent to an
c867dba1041640ecec7c8194d35a5b4ffce442earbowen address/port that is used for name-based vhosts. If the request
c867dba1041640ecec7c8194d35a5b4ffce442earbowen contained an unknown or no <code>Host:</code> header it is always
c867dba1041640ecec7c8194d35a5b4ffce442earbowen served from the primary name-based vhost (the vhost for that
c867dba1041640ecec7c8194d35a5b4ffce442earbowen address/port appearing first in the configuration file).</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>You can use <code class="directive"><a href="/mod/mod_alias.html#aliasmatch">AliasMatch</a></code> or
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code class="directive"><a href="/mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> to rewrite any
c867dba1041640ecec7c8194d35a5b4ffce442earbowen request to a single information page (or script).</p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <h3><a name="defaultdifferentports" id="defaultdifferentports"><code>_default_</code> vhosts
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>Same as setup 1, but the server listens on several ports and we want
c867dba1041640ecec7c8194d35a5b4ffce442earbowen to use a second <code>_default_</code> vhost for port 80.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <div class="example"><h3>Server configuration</h3><p><code>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost _default_:80><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor # ...<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost _default_:*><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # ...<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>The default vhost for port 80 (which <em>must</em> appear before any
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor default vhost with a wildcard port) catches all requests that were sent
c867dba1041640ecec7c8194d35a5b4ffce442earbowen to an unspecified IP address. The main server is never used to serve a
c867dba1041640ecec7c8194d35a5b4ffce442earbowen request.</p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <h3><a name="defaultoneport" id="defaultoneport"><code>_default_</code> vhosts
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>We want to have a default vhost for port 80, but no other default
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor vhosts.</p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <div class="example"><h3>Server configuration</h3><p><code>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost _default_:80><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>A request to an unspecified address on port 80 is served from the
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor default vhost any other request to an unspecified address and port is
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor served from the main server.</p>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor<h2><a name="migrate" id="migrate">Migrating a name-based vhost to an
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>The name-based vhost with the hostname
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <code>www.example2.org</code> (from our <a href="#name">name-based</a> example, setup 2) should get its own IP
c867dba1041640ecec7c8194d35a5b4ffce442earbowen address. To avoid problems with name servers or proxies who cached the
c867dba1041640ecec7c8194d35a5b4ffce442earbowen old IP address for the name-based vhost we want to provide both
c867dba1041640ecec7c8194d35a5b4ffce442earbowen variants during a migration phase.<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen The solution is easy, because we can simply add the new IP address
c867dba1041640ecec7c8194d35a5b4ffce442earbowen (<code>172.20.30.50</code>) to the <code>VirtualHost</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen directive.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <div class="example"><h3>Server configuration</h3><p><code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen Listen 80<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen NameVirtualHost 172.20.30.40<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.40 172.20.30.50><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # ...<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.40><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # ...<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>The vhost can now be accessed through the new address (as an
c867dba1041640ecec7c8194d35a5b4ffce442earbowen IP-based vhost) and through the old address (as a name-based
c867dba1041640ecec7c8194d35a5b4ffce442earbowen vhost).</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </div><div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<h2><a name="serverpath" id="serverpath">Using the <code>ServerPath</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <p>We have a server with two name-based vhosts. In order to match the
c867dba1041640ecec7c8194d35a5b4ffce442earbowen correct virtual host a client must send the correct <code>Host:</code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen header. Old HTTP/1.0 clients do not send such a header and Apache has
c867dba1041640ecec7c8194d35a5b4ffce442earbowen no clue what vhost the client tried to reach (and serves the request
c867dba1041640ecec7c8194d35a5b4ffce442earbowen from the primary vhost). To provide as much backward compatibility as
c867dba1041640ecec7c8194d35a5b4ffce442earbowen possible we create a primary vhost which returns a single page
c867dba1041640ecec7c8194d35a5b4ffce442earbowen containing links with an URL prefix to the name-based virtual
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <div class="example"><h3>Server configuration</h3><p><code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen NameVirtualHost 172.20.30.40<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.40><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # primary vhost<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen RewriteEngine On<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen # ...<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen </VirtualHost><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <VirtualHost 172.20.30.40><br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen ServerPath /sub1/<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor RewriteEngine On<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor # ...<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <VirtualHost 172.20.30.40><br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor ServerPath /sub2/<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor RewriteEngine On<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor # ...<br />
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor </VirtualHost>
dc3a272f8afcbc137adcfee4c3aa052d2bdf4df7gryzor <p>Due to the <code class="directive"><a href="/mod/core.html#serverpath">ServerPath</a></code>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen directive a request to the URL
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code>http://www.sub1.domain.tld/sub1/</code> is <em>always</em> served
c867dba1041640ecec7c8194d35a5b4ffce442earbowen from the sub1-vhost.<br /> A request to the URL
c867dba1041640ecec7c8194d35a5b4ffce442earbowen served from the sub1-vhost if the client sent a correct
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code>Host:</code> header. If no <code>Host:</code> header is sent the
c867dba1041640ecec7c8194d35a5b4ffce442earbowen client gets the information page from the primary host.<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen Please note that there is one oddity: A request to
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code>http://www.sub2.domain.tld/sub1/</code> is also served from the
c867dba1041640ecec7c8194d35a5b4ffce442earbowen sub1-vhost if the client sent no <code>Host:</code> header.<br />
c867dba1041640ecec7c8194d35a5b4ffce442earbowen The <code class="directive"><a href="/mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directives
c867dba1041640ecec7c8194d35a5b4ffce442earbowen are used to make sure that a client which sent a correct
c867dba1041640ecec7c8194d35a5b4ffce442earbowen <code>Host:</code> header can use both URL variants, <em>i.e.</em>,
c867dba1041640ecec7c8194d35a5b4ffce442earbowen with or without URL prefix.</p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<p><span>Available Languages: </span><a href="/en/vhosts/examples.html"> en </a></p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<p class="apache">Maintained by the <a href="http://httpd.apache.org/docs-project/">Apache HTTP Server Documentation Project</a></p>
c867dba1041640ecec7c8194d35a5b4ffce442earbowen<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>