From a415f220d45a3261cbf0557a5ea7d6341aa3949e Mon Sep 17 00:00:00 2001 From: Lars Eilebrecht Date: Sun, 14 Feb 1999 14:26:49 +0000 Subject: [PATCH] fix/enhancement PR: 3745 Submitted by: Roger Pack git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@82804 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/vhosts/details.html | 2 +- docs/manual/vhosts/name-based.html | 9 ++++++--- docs/manual/vhosts/name-based.html.en | 9 ++++++--- 3 files changed, 13 insertions(+), 7 deletions(-) diff --git a/docs/manual/vhosts/details.html b/docs/manual/vhosts/details.html index 8a69668b7a..f14bd088a5 100644 --- a/docs/manual/vhosts/details.html +++ b/docs/manual/vhosts/details.html @@ -126,7 +126,7 @@ set. Note that subsequent Port statements for this vhost will not affect the ports assigned in the address set.

During initialization a list for each IP address -is generated an inserted into an hash table. If the IP address is +is generated and inserted into an hash table. If the IP address is used in a NameVirtualHost directive the list contains all name-based vhosts for the given IP address. If there are no vhosts defined for that address the NameVirtualHost directive diff --git a/docs/manual/vhosts/name-based.html b/docs/manual/vhosts/name-based.html index 879e1ed73d..238cf5c721 100644 --- a/docs/manual/vhosts/name-based.html +++ b/docs/manual/vhosts/name-based.html @@ -107,15 +107,18 @@ For example, if local users are familiar with typing "www" or "www.foobar" then you will need to add ServerAlias www www.foobar. It isn't possible for the server to know what domain the client uses for their name resolution -because the client doesn't provide that information in the request.

+because the client doesn't provide that information in the request. +The ServerAlias directive is generally a way to have different +hostnames pointing to the same virtual host. +

Compatibility with Older Browsers

As mentioned earlier, there are still some clients in use who do not send the required data for the name-based virtual hosts to work properly. These clients will always be sent the pages from the -primary name-based virtual host (the first virtual host -appearing in the configuration file for a specific IP address).

+first virtual host listed for that IP address (the +primary name-based virtual host).

There is a possible workaround with the ServerPath diff --git a/docs/manual/vhosts/name-based.html.en b/docs/manual/vhosts/name-based.html.en index 879e1ed73d..238cf5c721 100644 --- a/docs/manual/vhosts/name-based.html.en +++ b/docs/manual/vhosts/name-based.html.en @@ -107,15 +107,18 @@ For example, if local users are familiar with typing "www" or "www.foobar" then you will need to add ServerAlias www www.foobar. It isn't possible for the server to know what domain the client uses for their name resolution -because the client doesn't provide that information in the request.

+because the client doesn't provide that information in the request. +The ServerAlias directive is generally a way to have different +hostnames pointing to the same virtual host. +

Compatibility with Older Browsers

As mentioned earlier, there are still some clients in use who do not send the required data for the name-based virtual hosts to work properly. These clients will always be sent the pages from the -primary name-based virtual host (the first virtual host -appearing in the configuration file for a specific IP address).

+first virtual host listed for that IP address (the +primary name-based virtual host).

There is a possible workaround with the ServerPath -- 2.50.1