From: Rich Bowen Date: Sat, 22 Jun 2002 19:49:34 +0000 (+0000) Subject: Largely rewritten, based on feedback on the list, on IRC, and questions X-Git-Tag: 2.0.40~411 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=04b22cbd50016785f738f97c46e6b32e7f7ea20d;p=apache Largely rewritten, based on feedback on the list, on IRC, and questions on usenet. Hopefully this is a little more what people are actually looking for, and will steer people towards better practices. Quite a lot of work still needs to be done, but this is the first cut, and, I think, somewhat of an improvement. Comments solicited. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95849 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/vhosts/examples.html b/docs/manual/vhosts/examples.html index a1c3e3fe94..94c3f32f24 100644 --- a/docs/manual/vhosts/examples.html +++ b/docs/manual/vhosts/examples.html @@ -1,535 +1,616 @@ - - -VirtualHost Examples - - - - - -

Virtual Host examples for common setups

- - -

Base configuration

- -

Simple name-based vhosting -
More complicated name-based vhosts -
IP-based vhosts -
Mixed name-/IP-based vhosts -
Port-based vhosts -

- -

Additional features

- -

Using _default_ vhosts -
Migrating a named-based vhost to an IP-based vhost -
Using the ServerPath directive -

- -

Simple name-based vhosting

- -

Setup: - The server machine has a primary name server.domain.tld. - There are two aliases (CNAMEs) www.domain.tld and - www.sub.domain.tld for the address server.domain.tld. -

- Server configuration: - -

- ... + + + + + + + VirtualHost Examples + + + + + + +

Virtual Host examples for common setups

+ +

This document attempts to answer the commonly-asked questions about + setting up virtual hosts. These scenarios are those involving multiple + web sites running on a single server, via name-based or IP-based virtual hosts. A document should be + coming soon about running sites on several servers behind a single + proxy server.

+ +

Examples

+ +

Running several name-based web sites on + a single IP address.
Name-based hosts on more than one IP + address.
Serving the same content on different IP + addresses (such as an internal and external address).
Running different sites on different + ports.
IP-based virtual hosting
Mixed port-based and ip-based virtual + hosts
Mixed name-based and IP-based vhosts

+ + + +

Additional features

+ +

Using _default_ vhosts
Migrating a named-based vhost to an IP-based + vhost
Using the ServerPath + directive

+ +

Running several name-based web + sites on a single IP address.

+ + + +

Setup:

+ +

Your server has a single IP address, and multiple aliases (CNAMES) + point to this machine in DNS. You want to run a web server for + www.example1.com and www.example2.org on this + machine.

+ +

+ + + + +
Note: Creating virtual + host configurations on your Apache server does not magically + cause DNS entries to be created for those host names. You + must have the names in DNS, resolving to your IP + address, or nobody else will be able to see your web site. You + can put entries in your hosts file for local + testing, but that will work only from the machine with those + hosts entries.
+

+ +

Server configuration:

+ +

+ + + + +
+
+    # Ensure that Apache listens on port 80
     Listen 80
-    ServerName server.domain.tld
 
+    # Listen for virtual host requests on all IP addresses
     NameVirtualHost *
 
     <VirtualHost *>
-    DocumentRoot /www/domain
-    ServerName www.domain.tld
-    ...
+        DocumentRoot /www/example1
+        ServerName www.example1.com
+
+        # Other directives here
+
     </VirtualHost>
     
     <VirtualHost *>
-    DocumentRoot /www/subdomain
-    ServerName www.sub.domain.tld
-    ...
-    </VirtualHost> 
-    
- The asterisks match all addresses, so the main server serves no - requests. Due to the fact that www.domain.tld is first - in the configuration file, it has the highest priority and can be - seen as the default or primary server. - -
- - - -
+ DocumentRoot /www/example2 + ServerName www.example2.org + + # Other directives here -
More complicated name-based vhosts
+ </VirtualHost> + +
+

+ +

The asterisks match all addresses, so the main server serves no + requests. Due to the fact that www.example1.com is first + in the configuration file, it has the highest priority and can be seen + as the default or primary server. That means + that if a request is received that does not match one of the specified + ServerName directives, it will be served by this first + VirtualHost.

+ +

+ + + + +
+ Note: + +
You can, if you wish, replace * with the actual + IP address of the system. In that case, the argument to + VirtualHost must match the argument to + NameVirtualHost:
+ +
+ + + + +
+
+    NameVirtualHost 12.34.56.78
+    <VirtualHost 12.34.56.78>
+        # etc ...
+
+
+
+ +
However, it is additionally useful to use * + on systems where the IP address is not predictable - for + example if you have a dynamic IP address with your ISP, and + you are using some variety of dynamic DNS solution. Since + * matches any IP address, this configuration + would work without changes whenever your IP address + changes.
+
+

+ +

The above configuration is what you will want to use in almost + all name-based virtual hosting situations. The only think that this + configuration will not work for, in fact, is when you are serving + different content based on differing IP addresses or ports.

+ +

Name-based hosts on more than one + IP address.

+ +

+ + + + +
Note: Any of the + techniques discussed here can be extended to any number of IP + addresses.
+

+ Setup 1: + +

The server has two IP addresses. On one (1.2.3.4), we + will serve the "main" server, and on the other (5.6.7.8), + we will serve two or more virtual hosts.

+ +

Server configuration:

+ +

+ + + + +

+    Listen 80
 
-
+    # This is the "main" server
+    ServerName server.domain.com
+    DocumentRoot /www/mainserver
 
-Setup 1:
-    The server machine has one IP address (111.22.33.44)
-    which resolves to the name server.domain.tld.
-    There are two aliases (CNAMEs) www.domain.tld and
-    www.sub.domain.tld for the address 111.22.33.44.
-    
-    Server configuration:
+    # This is the other address
+    NameVirtualHost 5.6.7.8
 
-    
-    ...
-    Listen 80
-    ServerName server.domain.tld
-
-    NameVirtualHost 111.22.33.44 
+    <VirtualHost 5.6.7.8>
+        DocumentRoot /www/example1
+        ServerName www.example1.com
+    
+        # Other directives here ...
 
-    <VirtualHost 111.22.33.44>
-    DocumentRoot /www/domain
-    ServerName www.domain.tld
-    ...
     </VirtualHost>
     
-    <VirtualHost 111.22.33.44>
-    DocumentRoot /www/subdomain
-    ServerName www.sub.domain.tld
-    ...
-    </VirtualHost> 
-    
-    Apart from localhost there are no unspecified
-    addresses/ports, therefore the main server only serves
-    localhost requests. Due to the fact
-    that www.domain.tld has the highest priority
-    it can be seen as the default or
-    primary server.
-    
-    
-   
-
Setup 2:
-    The server machine has two IP addresses (111.22.33.44
-    and 111.22.33.55)
-    which resolve to the names server1.domain.tld and
-    server2.domain.tld respectively.
-    The alias www.domain.tld should be used for the
-    main server which should also catch any unspecified addresses. 
-    We want to use a virtual host for the alias
-    www.otherdomain.tld and another virtual host, 
-    with server name www.sub.domain.tld, should
-    catch any request to hostnames of the form
-    *.sub.domain.tld. 
-    The address 111.22.33.55 should be
-    used for the virtual hosts.
-    
-    Server configuration:
-
-    
-    ...
-    Listen 80
-    ServerName www.domain.tld
-    DocumentRoot /www/domain
-
-    NameVirtualHost 111.22.33.55
+    <VirtualHost 5.6.7.8>
+        DocumentRoot /www/example2
+        ServerName www.example2.org
+    
+        # Other directives here ...
 
-    <VirtualHost 111.22.33.55>
-    DocumentRoot /www/otherdomain
-    ServerName www.otherdomain.tld
-    ...
-    </VirtualHost>
-   
-    <VirtualHost 111.22.33.55>
-    DocumentRoot /www/subdomain
-    ServerName www.sub.domain.tld
-    ServerAlias *.sub.domain.tld
-    ...
     </VirtualHost> 
-    
-    Any request to an address other than 111.22.33.55
-    will be served from the main server. A request to
-    111.22.33.55 with an unknown or no Host:
-    header will be served from www.otherdomain.tld.
-    
-
-
Setup 3:
-       The server machine has two IP addresses (192.168.1.1
-       and 111.22.33.55). The machine is sitting between
-       an internal (intranet) network and an external (internet) network.
-       Outside of the network, the name server1.domain.tld
-       resolves to the external address (111.22.33.55), but
-       inside the network, that same name resolves to the internal
-       address (192.168.1.1).
-
-       The server can be made to respond to internal and external
-       requests with the same content, with just one VirtualHost
-       section.
-       

-
-       Server configuration:
-
-       
-    ...
+
+

+ +

Any request to an address other than 5.6.7.8 will be + served from the main server. A request to 5.6.7.8 with an + unknown hostname, or no Host: header, will be served from + www.example1.com.

+ +

Serving the same content on + different IP addresses (such as an internal and external + address).

+ + Setup: + +

The server machine has two IP addresses (192.168.1.1 + and 11.22.33.44). The machine is sitting between an + internal (intranet) network and an external (internet) network. Outside + of the network, the name server.example.com resolves to + the external address (111.22.33.55), but inside the + network, that same name resolves to the internal address + (192.168.1.1).

+ +

The server can be made to respond to internal and external requests + with the same content, with just one VirtualHost + section.

+ +

Server configuration:

+ +

+ + + + +
+
     NameVirtualHost 192.168.1.1
-    NameVirtualHost 111.22.33.55
+    NameVirtualHost 11.22.33.44
 
-    <VirtualHost 192.168.1.1 111.22.33.55>
-    DocumentRoot /www/server1
-    ServerName server1.domain.tld
-    ServerAlias server1
-    ...
+    <VirtualHost 192.168.1.1 11.22.33.44>
+        DocumentRoot /www/server1
+        ServerName server.example.com
+        ServerAlias server
     </VirtualHost>
-    
- - Now requests from both networks will be served from the same - VirtualHost - -
Setup 4: - You have multiple domains going to the same IP and also want - to serve multiple ports. By defining the - ports in the "NameVirtualHost" tag, you can allow this to - work. If you try using without the - NameVirtualHost name:port or you try to use the Listen - directive, your configuration will not work. -
- - Server configuration: + +
+

+ +

Now requests from both networks will be served from the same + VirtualHost.

+ +

+ + + + +
Note: On the internal + network, one can just use the name server rather + than the fully qualified host name server.example.com. Note + also that, in the above example, you can replace the list of IP + addresses with *, which will cause the server to respond + the same on all addresses.
+

+ +

Running different sites on different + ports.

+ +

Setup:

+ +

You have multiple domains going to the same IP and also want to + serve multiple ports. By defining the ports in the "NameVirtualHost" + tag, you can allow this to work. If you try using <VirtualHost + name:port> without the NameVirtualHost name:port or you try to use + the Listen directive, your configuration will not work.

+ +

Server configuration:

+ +

+ + + + +

+    Listen 80
+    Listen 8080
 
-       -    ...   
-    NameVirtualHost 111.22.33.44:80
-    NameVirtualHost 111.22.33.44:8080
+    NameVirtualHost 11.22.33.44:80
+    NameVirtualHost 11.22.33.44:8080
 
-    <VirtualHost 111.22.33.44:80>
-    ServerName www.domain.tld
-    DocumentRoot /www/domain-80
+    <VirtualHost 11.22.33.44:80>
+        ServerName www.domain.tld
+        DocumentRoot /www/domain-80
     </VirtualHost>
 
-    <VirtualHost 111.22.33.44:8080>
-    ServerName www.domain.tld
-    DocumentRoot /www/domain-8080
+    <VirtualHost 11.22.33.44:8080>
+        ServerName www.domain.tld
+        DocumentRoot /www/domain-8080
     </VirtualHost>
 
-    <VirtualHost 111.22.33.44:80>
-    ServerName www.otherdomain.tld
-    DocumentRoot /www/otherdomain-80
+    <VirtualHost 11.22.33.44:80>
+        ServerName www.otherdomain.tld
+        DocumentRoot /www/otherdomain-80
     </VirtualHost>
 
-    <VirtualHost 111.22.33.44:8080>
-    ServerName www.otherdomain.tld
-    DocumentRoot /www/otherdomain-8080
+    <VirtualHost 11.22.33.44:8080>
+        ServerName www.otherdomain.tld
+        DocumentRoot /www/otherdomain-8080
     </VirtualHost>
+
+

IP-based virtual hosting

Setup:

The server has two IP addresses (1.2.3.4 and + 5.6.7.8) which resolve to the names + www.example1.com and www.example2.org + respectively.

IP-based vhosts

Server configuration:

Setup 1: - The server machine has two IP addresses (111.22.33.44 - and 111.22.33.55) - which resolve to the names server.domain.tld and - www.otherdomain.tld respectively. - The hostname www.domain.tld is an alias (CNAME) - for server.domain.tld and will represent the - main server. -

- Server configuration: - - -

- ... +

+ + + + +
+
     Listen 80
-    DocumentRoot /www/domain
-    ServerName www.domain.tld
 
-    <VirtualHost 111.22.33.55>
-    DocumentRoot /www/otherdomain
-    ServerName www.otherdomain.tld
-    ...
+    <VirtualHost 1.2.3.4>
+        DocumentRoot /www/example1
+        ServerName www.example1.com
     </VirtualHost>
-    
- www.otherdomain.tld can only be reached through the - address 111.22.33.55, while www.domain.tld - can only be reached through 111.22.33.44 - (which represents our main server). - -
- -
Setup 2: - Same as setup 1, but we don't want to have a dedicated main server. -
- Server configuration: - -
-    ...
-    Listen 80
-    ServerName server.domain.tld
+   
+    <VirtualHost 5.6.7.8>
+        DocumentRoot /www/example2
+        ServerName www.example2.org
+    </VirtualHost>
+
+
+

+ +

Requests for any address not specified in one of the + <VirtualHost> directives (such as + localhost, for example) will go to the main server, if + there is one.

+ +

Mixed port-based and ip-based + virtual hosts

+ +

Setup:

+ +

The server machine has two IP addresses (1.2.3.4 and + 5.6.7.8) which resolve to the names + www.example1.com and www.example2.org + respectively. In each case, we want to run hosts on ports 80 and + 8080.

+ +

+ + + + +
+
+    Listen 1.2.3.4:80
+    Listen 1.2.3.4:8080
+    Listen 5.6.7.8:80
+    Listen 5.6.7.8:8080
     
-    <VirtualHost 111.22.33.44>
-    DocumentRoot /www/domain
-    ServerName www.domain.tld
-    ...
+    <VirtualHost 1.2.3.4:80>
+        DocumentRoot /www/example1-80
+        ServerName www.example1.com
     </VirtualHost>
 
-    <VirtualHost 111.22.33.55>
-    DocumentRoot /www/otherdomain
-    ServerName www.otherdomain.tld
-    ...
+    <VirtualHost 1.2.3.4:8080>
+        DocumentRoot /www/example1-8080
+        ServerName www.example1.com
     </VirtualHost>
-    
- The main server can never catch a request, because all IP addresses - of our machine are in use for IP-based virtual hosts - (only localhost requests can hit the main server). - -
- -
Setup 3: - The server machine has two IP addresses (111.22.33.44 - and 111.22.33.55) - which resolve to the names server.domain.tld and - www-cache.domain.tld respectively. - The hostname www.domain.tld is an alias (CNAME) - for server.domain.tld and will represent the - main server. - www-cache.domain.tld will become our proxy-cache - listening on port 8080, while the web server itself uses the default - port 80. -
- Server configuration: - -
-    ...
-    Listen 111.22.33.44:80
-    Listen 111.22.33.55:8080
-    ServerName server.domain.tld
     
-    <VirtualHost 111.22.33.44:80>
-    DocumentRoot /www/domain
-    ServerName www.domain.tld
-    ...
+    <VirtualHost 5.6.7.8:80>
+        DocumentRoot /www/example2-80
+        ServerName www.example1.org
     </VirtualHost>
 
-    <VirtualHost 111.22.33.55:8080>
-    ServerName www-cache.domain.tld
-    ...
-      <Directory proxy:>
-      Order Deny,Allow
-      Deny from all
-      Allow from 111.22.33
-      </Directory>
+    <VirtualHost 5.6.7.8:8080>
+        DocumentRoot /www/example2-8080
+        ServerName www.example2.org
     </VirtualHost>
-    
- The main server can never catch a request, because all IP addresses - (apart from localhost) of our machine are in use for IP-based - virtual hosts. The web server can only be reached on the first address - through port 80 and the proxy only on the second address through port 8080. -
- - -
- -
Mixed name-/IP-based vhosts
- -
- -
Setup: - The server machine has three IP addresses (111.22.33.44, - 111.22.33.55 and 111.22.33.66) - which resolve to the names server.domain.tld, - www.otherdomain1.tld and www.otherdomain2.tld - respectively. - The address 111.22.33.44 should be used for a couple - of name-based vhosts and the other addresses for IP-based vhosts. -
- Server configuration: - -
-    ...
+
+
+

+ +

Mixed name-based and IP-based + vhosts

+ +

Setup:

+ +

On some of my addresses, I want to do name-based virtual hosts, and + on others, IP-based hosts.

+ +

Server configuration:

+ +

+ + + + +

     Listen 80
-    ServerName server.domain.tld
 
-    NameVirtualHost 111.22.33.44
+    NameVirtualHost 1.2.3.4
 
-    <VirtualHost 111.22.33.44>
-    DocumentRoot /www/domain
-    ServerName www.domain.tld
-    ...
+    <VirtualHost 1.2.3.4>
+        DocumentRoot /www/example1
+        ServerName www.example1.com
     </VirtualHost>
    
-    <VirtualHost 111.22.33.44>
-    DocumentRoot /www/subdomain1
-    ServerName www.sub1.domain.tld
-    ...
+    <VirtualHost 1.2.3.4>
+        DocumentRoot /www/example2
+        ServerName www.example2.org
     </VirtualHost> 
     
-    <VirtualHost 111.22.33.44>
-    DocumentRoot /www/subdomain2
-    ServerName www.sub2.domain.tld
-    ...
+    <VirtualHost 1.2.3.4>
+        DocumentRoot /www/example3
+        ServerName www.example3.net
     </VirtualHost> 
- 
-    <VirtualHost 111.22.33.55>
-    DocumentRoot /www/otherdomain1
-    ServerName www.otherdomain1.tld
-    ...
+
+    # IP-based
+    <VirtualHost 5.6.7.8>
+        DocumentRoot /www/example4
+        ServerName www.example4.edu
     </VirtualHost> 
     
-    <VirtualHost 111.22.33.66>
-    DocumentRoot /www/otherdomain2
-    ServerName www.otherdomain2.tld
-    ...
+    <VirtualHost 9.8.7.6>
+        DocumentRoot /www/example5
+        ServerName www.example5.gov
     </VirtualHost>     
-

+ +

Using `_default_` + vhosts

Setup 1:

Port-based vhosts

Catching every request to any unspecified IP address and + port, i.e., an address/port combination that is not used for + any other virtual host.

Server configuration:

Setup: - The server machine has one IP address (111.22.33.44) - which resolves to the name www.domain.tld. - If we don't have the option to get another address or alias - for our server we can use port-based vhosts if we need - a virtual host with a different configuration. -
- Server configuration: +
+ + + + +
+
+ <VirtualHost _default_:*> + DocumentRoot /www/default + </VirtualHost> +
+
+
-
```
-    ...
-    Listen 80
-    Listen 8080
-    ServerName www.domain.tld
-    DocumentRoot /www/domain
+    Using such a default vhost with a wildcard port effectively prevents
+    any request going to the main server.
 
-    <VirtualHost 111.22.33.44:8080>
-    DocumentRoot /www/domain2
-    ...
-    </VirtualHost>
-    
```
- A request to www.domain.tld on port 80 is served - from the main server and a request to port 8080 is served from - the virtual host. -
-

- -

A default vhost never serves a request that was sent to an + address/port that is used for name-based vhosts. If the request + contained an unknown or no Host: header it is always + served from the primary name-based vhost (the vhost for that + address/port appearing first in the configuration file).

Using `_default_` vhosts

You can use AliasMatch or + RewriteRule + to rewrite any request to a single information page (or script).

Setup 2:

Setup 1: - Catching every request to any unspecified IP address and port, - i.e., an address/port combination that is not used for any other - virtual host. -
- Server configuration: +
Same as setup 1, but the server listens on several ports and we want + to use a second _default_ vhost for port 80.
-
```
-    ...
-    <VirtualHost _default_:*>
-    DocumentRoot /www/default
-    ...
-    </VirtualHost>
-    
```
- Using such a default vhost with a wildcard port effectively - prevents any request going to the main server.
- A default vhost never serves a request that was sent to an - address/port that is used for name-based vhosts. If the request - contained an unknown or no Host: header it is - always served from the primary name-based vhost (the - vhost for that address/port appearing first in the configuration - file).
- You can use - AliasMatch - or - RewriteRule - to rewrite any request to a single information page (or script). -
-
- -

Setup 2: - Same as setup 1, but the server listens on several ports and - we want to use a second _default_ vhost for port 80. -

- Server configuration: +

Server configuration:

-    ...
+    
+      
+        
+          
+        
+      
+     <VirtualHost _default_:80>
-    DocumentRoot /www/default80
-    ...
+        DocumentRoot /www/default80
+        # ...
     </VirtualHost>
     
     <VirtualHost _default_:*>
-    DocumentRoot /www/default
-    ...
+        DocumentRoot /www/default
+        # ...
     </VirtualHost>    
-    
-    The default vhost for port 80 (which must appear before
-    any default vhost with a wildcard port) catches all requests that
-    were sent to an unspecified IP address. The main server is
-    never used to serve a request.
-        
-    
-    
-
Setup 3: 
-    We want to have a default vhost for port 80, but no other default vhosts.
-    
-    Server configuration:
-
-    
-    ...
-    <VirtualHost _default_:80>
-    DocumentRoot /www/default
-    ...
-    </VirtualHost>
-    
-    A request to an unspecified address on port 80 is served from the
-    default vhost any other request to an unspecified address and port
-    is served from the main server.
-    
+
+          
+    
 
-

The default vhost for port 80 (which must appear before any + default vhost with a wildcard port) catches all requests that were sent + to an unspecified IP address. The main server is never used to serve a + request.

Setup 3:

Migrating a name-based vhost to an IP-based vhost

We want to have a default vhost for port 80, but no other default + vhosts.

Server configuration:

Setup: - The name-based vhost with the hostname - www.otherdomain.tld (from our name-based - example, setup 2) should get its own IP address. - To avoid problems with name servers or proxies who cached the old - IP address for the name-based vhost we want to provide both variants - during a migration phase.
- The solution is easy, because we can simply add the new IP address - (111.22.33.66) to the VirtualHost directive. -

- Server configuration: - -

+    
+      
+        
+          
+        
+      
++    <VirtualHost _default_:80>
+    DocumentRoot /www/default
     ...
+    </VirtualHost>
+
+          
+    
+
+    A request to an unspecified address on port 80 is served from the
+    default vhost any other request to an unspecified address and port is
+    served from the main server.
+    
+
+    Migrating a name-based vhost to an
+    IP-based vhost
+
+    Setup:
+
+    The name-based vhost with the hostname
+    www.otherdomain.tld (from our name-based example, setup 2) should get its own IP
+    address. To avoid problems with name servers or proxies who cached the
+    old IP address for the name-based vhost we want to provide both
+    variants during a migration phase.

+     The solution is easy, because we can simply add the new IP address
+    (111.22.33.66) to the VirtualHost
+    directive.
+
+    Server configuration:
+
+    
+      
+        
+          
+        
+      
+     Listen 80
     ServerName www.domain.tld
     DocumentRoot /www/domain
@@ -537,90 +618,98 @@
     NameVirtualHost 111.22.33.55
 
     <VirtualHost 111.22.33.55 111.22.33.66>
-    DocumentRoot /www/otherdomain
-    ServerName www.otherdomain.tld
-    ...
+        DocumentRoot /www/otherdomain
+        ServerName www.otherdomain.tld
+        # ...
     </VirtualHost>
    
     <VirtualHost 111.22.33.55>
-    DocumentRoot /www/subdomain
-    ServerName www.sub.domain.tld
-    ServerAlias *.sub.domain.tld
-    ...
+        DocumentRoot /www/subdomain
+        ServerName www.sub.domain.tld
+        ServerAlias *.sub.domain.tld
+        # ...
     </VirtualHost>
-    
-    The vhost can now be accessed through the new address (as an IP-based
-    vhost) and through the old address (as a name-based vhost).
-    
-
-
-
-
-
-Using the ServerPath directive
-
-
-
-Setup:
-    We have a server with two name-based vhosts. In order to match the correct
-    virtual host a client must send the correct Host: header.
-    Old HTTP/1.0 clients do not send such a header and Apache has no clue
-    what vhost the client tried to reach (and serves the request from
-    the primary vhost). To provide as much backward compatibility
-    as possible we create a primary vhost which returns a single page
-    containing links with an URL prefix to the name-based virtual hosts.
-    
-    Server configuration:
-
-    
-    ...
+
+          
+    
+
+    The vhost can now be accessed through the new address (as an
+    IP-based vhost) and through the old address (as a name-based
+    vhost).
+    
+
+    Using the
+    ServerPath directive
+
+    Setup:
+
+    We have a server with two name-based vhosts. In order to match the
+    correct virtual host a client must send the correct Host:
+    header. Old HTTP/1.0 clients do not send such a header and Apache has
+    no clue what vhost the client tried to reach (and serves the request
+    from the primary vhost). To provide as much backward compatibility as
+    possible we create a primary vhost which returns a single page
+    containing links with an URL prefix to the name-based virtual
+    hosts.
+
+    Server configuration:
+
+    
+      
+        
+          
+        
+      
+     NameVirtualHost 111.22.33.44
 
     <VirtualHost 111.22.33.44>
-    # primary vhost
-    DocumentRoot /www/subdomain
-    RewriteEngine On
-    RewriteRule ^/.* /www/subdomain/index.html
-    ...
+        # primary vhost
+        DocumentRoot /www/subdomain
+        RewriteEngine On
+        RewriteRule ^/.* /www/subdomain/index.html
+        # ...
     </VirtualHost>
 
     <VirtualHost 111.22.33.44>
     DocumentRoot /www/subdomain/sub1
-    ServerName www.sub1.domain.tld
-    ServerPath /sub1/
-    RewriteEngine On
-    RewriteRule ^(/sub1/.*) /www/subdomain$1 
-    ...
+        ServerName www.sub1.domain.tld
+        ServerPath /sub1/
+        RewriteEngine On
+        RewriteRule ^(/sub1/.*) /www/subdomain$1 
+        # ...
     </VirtualHost>
 
     <VirtualHost 111.22.33.44>
-    DocumentRoot /www/subdomain/sub2
-    ServerName www.sub2.domain.tld
-    ServerPath /sub2/
-    RewriteEngine On
-    RewriteRule ^(/sub2/.*) /www/subdomain$1 
-    ...
+        DocumentRoot /www/subdomain/sub2
+        ServerName www.sub2.domain.tld
+        ServerPath /sub2/
+        RewriteEngine On
+        RewriteRule ^(/sub2/.*) /www/subdomain$1 
+        # ...
     </VirtualHost>
-    
-    Due to the ServerPath
-    directive a request to the
-    URL http://www.sub1.domain.tld/sub1/ is always
-    served from the sub1-vhost. 

-    A request to the URL http://www.sub1.domain.tld/
-    is only served from the sub1-vhost if the client sent a correct
-    Host: header.
-    If no Host: header is sent the client gets the
-    information page from the primary host.

-    Please note that there is one oddity: A request to
-    http://www.sub2.domain.tld/sub1/ is also served from
-    the sub1-vhost if the client sent no Host: header. 

-    The RewriteRule directives are used to make sure that
-    a client which sent a correct Host: header can use
-    both URL variants, i.e., with or without URL prefix.
-    
-
- 
-
-
-
-
+
+          
+    
+
+    Due to the ServerPath
+    directive a request to the URL
+    http://www.sub1.domain.tld/sub1/ is always served
+    from the sub1-vhost.

+     A request to the URL http://www.sub1.domain.tld/ is only
+    served from the sub1-vhost if the client sent a correct
+    Host: header. If no Host: header is sent the
+    client gets the information page from the primary host.

+     Please note that there is one oddity: A request to
+    http://www.sub2.domain.tld/sub1/ is also served from the
+    sub1-vhost if the client sent no Host: header.

+     The RewriteRule directives are used to make sure that a
+    client which sent a correct Host: header can use both URL
+    variants, i.e., with or without URL prefix.
+    
+  
+
+

Virtual Host examples for common setups

Base configuration

Additional features

Simple name-based vhosting

Virtual Host examples for common setups

Examples

Additional features

Running several name-based web + sites on a single IP address.

More complicated name-based vhosts

Name-based hosts on more than one + IP address.

Serving the same content on + different IP addresses (such as an internal and external + address).

Running different sites on different + ports.

IP-based virtual hosting

IP-based vhosts

Mixed port-based and ip-based + virtual hosts

Mixed name-/IP-based vhosts

Mixed name-based and IP-based + vhosts

Using `_default_` + vhosts

Port-based vhosts

Using `_default_` vhosts

Migrating a name-based vhost to an IP-based vhost

Migrating a name-based vhost to an + IP-based vhost

Using the `ServerPath` directive

Using the + `ServerPath` directive