From: Astrid Malo NameVirtualHost
directive.
In the normal case where any and all IP addresses on the server should
be used, you can use *
as the argument to
- NameVirtualHost
. Note that mentioning an IP address in a
- NameVirtualHost
directive does not automatically make the
- server listen to that IP address. See Setting
- which addresses and ports Apache uses for more details. In addition,
- any IP address specified here must be associated with a network interface
+ NameVirtualHost
. Note that mentioning an
+ IP address in a NameVirtualHost
directive
+ does not automatically make the server listen to that IP address. See
+ Setting which addresses and ports Apache uses
+ for more details. In addition, any IP address specified here must be
+ associated with a network interface
on the server.
The next step is to create a <VirtualHost>
block for
each different host that you would like to serve. The argument to the
- <VirtualHost>
directive should be the same as the
- argument to the NameVirtualHost
directive (ie, an IP
- address, or *
for all addresses). Inside each
- <VirtualHost>
block, you will need at minimum a
+ <VirtualHost>
directive
+ should be the same as the argument to the NameVirtualHost
directive (ie, an IP address,
+ or *
for all addresses). Inside each <VirtualHost>
block, you will need at minimum a
ServerName
directive to
designate which host is served and a DocumentRoot
directive to
show where in the filesystem the content for that host lives.
ServerName
and DocumentRoot
included in
- this virtual host should be the same as the global
- ServerName
and DocumentRoot
. List this
- virtual host first in the configuration file so that it will act as
- the default host.
+ must also create a <VirtualHost>
block for the existing host.
+ The ServerName
and
+ DocumentRoot
included in this virtual
+ host should be the same as the global ServerName
and DocumentRoot
. List this virtual host first in
+ the configuration file so that it will act as the default host.
For example, suppose that you are serving the domain @@ -130,18 +129,17 @@
You can alternatively specify an explicit IP address in place of
- the * in both the NameVirtualHost
and
- <VirtualHost>
directives. For example, you might
- want to do this in order to run some name-based virtual hosts on one
- IP address, and either IP-based, or another set of name-based
- virtual hosts on another address.
*
in both the NameVirtualHost
and <VirtualHost>
directives.
+ For example, you might want to do this in order to run some name-based virtual
+ hosts on one IP address, and either IP-based, or another set of name-based
+ virtual hosts on another address.
Many servers want to be accessible by more than one name. This is
possible with the ServerAlias
- directive, placed inside the <VirtualHost> section. For
- example in the first <VirtualHost> block above, the ServerAlias
directive indicates that the
- listed names are other names which people can use to see that same
- web site:
<VirtualHost>
section. For
+ example in the first <VirtualHost>
block above, the ServerAlias
directive indicates that the
+ listed names are other names which people can use to see that same
+ web site:
then requests for all hosts in the
ServerAlias domain.tld *.domain.tld
@@ -149,41 +147,39 @@
domain.tld
domain
will be served by the www.domain.tld
virtual host. The
- wildcard characters * and ? can be used to match names. Of course,
- you can't just make up names and place them in ServerName
- or ServerAlias
. You must first have your DNS server
- properly configured to map those names to an IP address associated
- with your server.*
and ?
can be used to match
+ names. Of course, you can't just make up names and place them in ServerName
or ServerAlias
.
+ You must first have your DNS server properly configured to map those names
+ to an IP address associated with your server.
Finally, you can fine-tune the configuration of the virtual hosts
by placing other directives inside the
- <VirtualHost>
containers. Most directives can be
- placed in these containers and will then change the configuration only
- of the relevant virtual host. To find out if a particular directive
- is allowed, check the Context of the
+ <VirtualHost>
containers.
+ Most directives can be placed in these containers and will then change the
+ configuration only of the relevant virtual host. To find out if a particular
+ directive is allowed, check the Context of the
directive. Configuration directives set in the main server
- context (outside any <VirtualHost>
container)
- will be used only if they are not overridden by the virtual host
- settings.
<VirtualHost>
container) will be used only if they
+ are not overridden by the virtual host settings.
Now when a request arrives, the server will first check if it is
- using an IP address that matches the NameVirtualHost
. If
- it is, then it will look at each <VirtualHost>
- section with a matching IP address and try to find one where the
- ServerName
or ServerAlias
matches the
- requested hostname. If it finds one, then it uses the configuration
- for that server. If no matching virtual host is found, then
- the first listed virtual host that matches the IP
- address will be used.
NameVirtualHost
. If it is, then it will look at
+ each <VirtualHost>
+ section with a matching IP address and try to find one where the
+ ServerName
or
+ ServerAlias
matches the requested hostname. If it finds one,
+ then it uses the configuration for that server. If no matching virtual host
+ is found, then the first listed virtual host that matches
+ the IP address will be used.
As a consequence, the first listed virtual host is the
- default virtual host. The DocumentRoot
from the
+ default virtual host. The DocumentRoot
from the
main server will never be used when an IP
- address matches the NameVirtualHost
directive. If you
- would like to have a special configuration for requests that do not
- match any particular virtual host, simply put that configuration in a
- <VirtualHost>
container and list it first in the
- configuration file.
NameVirtualHost
+ directive. If you would like to have a special configuration for requests
+ that do not match any particular virtual host, simply put that configuration
+ in a <VirtualHost>
+ container and list it first in the configuration file.
What does this mean? It means that a request for any URI
beginning with "/domain
" will be served from the
- virtual host www.domain.tld
This means that the
- pages can be accessed as
- http://www.domain.tld/domain/
for all clients,
- although clients sending a Host:
header can also
- access it as http://www.domain.tld/
.
www.domain.tld
. This means that the
+ pages can be accessed as http://www.domain.tld/domain/
+ for all clients, although clients sending a Host:
header
+ can also access it as http://www.domain.tld/
.
In order to make this work, put a link on your primary
virtual host's page to
- http://www.domain.tld/domain/
Then, in the virtual
+ http://www.domain.tld/domain/
. Then, in the virtual
host's pages, be sure to use either purely relative links
(e.g., "file.html
" or
- "../icons/image.gif
" or links containing the
+ "../icons/image.gif
") or links containing the
prefacing /domain/
(e.g.,
"http://www.domain.tld/domain/misc/file.html
" or
"/domain/misc/file.html
").
*
as the argument to
- NameVirtualHost
. Note that mentioning an IP address in a
- NameVirtualHost
directive does not automatically make the
- server listen to that IP address. See Setting
- which addresses and ports Apache uses for more details. In addition,
- any IP address specified here must be associated with a network interface
+ The next step is to create a <VirtualHost>
directive should be the same as the
- argument to the NameVirtualHost
directive (ie, an IP
- address, or *
for all addresses). Inside each
- <VirtualHost>
block, you will need at minimum a
+ *
for all addresses). Inside each ServerName
and DocumentRoot
included in
- this virtual host should be the same as the global
- ServerName
and DocumentRoot
. List this
- virtual host first in the configuration file so that it will act as
- the default host.
+ must also create a
For example, suppose that you are serving the domain @@ -131,19 +135,22 @@
You can alternatively specify an explicit IP address in place of
- the * in both the NameVirtualHost
and
- <VirtualHost>
directives. For example, you might
- want to do this in order to run some name-based virtual hosts on one
- IP address, and either IP-based, or another set of name-based
- virtual hosts on another address.
*
in both the Many servers want to be accessible by more than one name. This is
possible with the
then requests for all hosts in the domain.tld
domain
will be served by the www.domain.tld
virtual host. The
- wildcard characters * and ? can be used to match names. Of course,
- you can't just make up names and place them in ServerName
- or ServerAlias
. You must first have your DNS server
- properly configured to map those names to an IP address associated
- with your server.
*
and ?
can be used to match
+ names. Of course, you can't just make up names and place them in ServerAlias
.
+ You must first have your DNS server properly configured to map those names
+ to an IP address associated with your server.
Finally, you can fine-tune the configuration of the virtual hosts
by placing other directives inside the
- <VirtualHost>
containers. Most directives can be
- placed in these containers and will then change the configuration only
- of the relevant virtual host. To find out if a particular directive
- is allowed, check the VirtualHost containers.
+ Most directives can be placed in these containers and will then change the
+ configuration only of the relevant virtual host. To find out if a particular
+ directive is allowed, check the Context of the
directive. Configuration directives set in the main server
- context (outside any <VirtualHost>
container)
- will be used only if they are not overridden by the virtual host
- settings.
Now when a request arrives, the server will first check if it is
- using an IP address that matches the NameVirtualHost
. If
- it is, then it will look at each <VirtualHost>
- section with a matching IP address and try to find one where the
- ServerName
or ServerAlias
matches the
- requested hostname. If it finds one, then it uses the configuration
- for that server. If no matching virtual host is found, then
- the first listed virtual host that matches the IP
- address will be used.
ServerAlias
matches the requested hostname. If it finds one,
+ then it uses the configuration for that server. If no matching virtual host
+ is found, then the first listed virtual host that matches
+ the IP address will be used.
As a consequence, the first listed virtual host is the
- default virtual host. The DocumentRoot
from the
+ default virtual host. The NameVirtualHost
directive. If you
- would like to have a special configuration for requests that do not
- match any particular virtual host, simply put that configuration in a
- <VirtualHost>
container and list it first in the
- configuration file.
What does this mean? It means that a request for any URI
beginning with "/domain
" will be served from the
- virtual host www.domain.tld
This means that the
- pages can be accessed as
- http://www.domain.tld/domain/
for all clients,
- although clients sending a Host:
header can also
- access it as http://www.domain.tld/
.
www.domain.tld
. This means that the
+ pages can be accessed as http://www.domain.tld/domain/
+ for all clients, although clients sending a Host:
header
+ can also access it as http://www.domain.tld/
.
In order to make this work, put a link on your primary
virtual host's page to
- http://www.domain.tld/domain/
Then, in the virtual
+ http://www.domain.tld/domain/
. Then, in the virtual
host's pages, be sure to use either purely relative links
(e.g., "file.html
" or
- "../icons/image.gif
" or links containing the
+ "../icons/image.gif
") or links containing the
prefacing /domain/
(e.g.,
"http://www.domain.tld/domain/misc/file.html
" or
"/domain/misc/file.html
").