From: Lars Eilebrecht 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 Port statements for this vhost will not
affect the ports assigned in the address set.
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 879e1ed73d1..238cf5c7211 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.ServerAlias directive is generally a way to have different
+hostnames pointing to the same virtual host.
+
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 879e1ed73d1..238cf5c7211 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.
ServerAlias directive is generally a way to have different
+hostnames pointing to the same virtual host.
+
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