Return-Path: Delivered-To: apache-cvs-archive@hyperreal.org Received: (qmail 9530 invoked by uid 6000); 14 Feb 1999 14:26:53 -0000 Received: (qmail 9520 invoked by alias); 14 Feb 1999 14:26:51 -0000 Delivered-To: apache-1.3-cvs@hyperreal.org Received: (qmail 9513 invoked by uid 220); 14 Feb 1999 14:26:50 -0000 Date: 14 Feb 1999 14:26:50 -0000 Message-ID: <19990214142650.9512.qmail@hyperreal.org> From: lars@hyperreal.org To: apache-1.3-cvs@hyperreal.org Subject: cvs commit: apache-1.3/htdocs/manual/vhosts details.html name-based.html Sender: apache-cvs-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org lars 99/02/14 06:26:50 Modified: htdocs/manual/vhosts details.html name-based.html Log: fix/enhancement PR: 3745 Submitted by: Roger Pack Revision Changes Path 1.10 +1 -1 apache-1.3/htdocs/manual/vhosts/details.html Index: details.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/vhosts/details.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- details.html 1998/09/17 14:52:03 1.9 +++ details.html 1999/02/14 14:26:49 1.10 @@ -126,7 +126,7 @@ 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 1.10 +6 -3 apache-1.3/htdocs/manual/vhosts/name-based.html Index: name-based.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/vhosts/name-based.html,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- name-based.html 1998/12/18 23:49:44 1.9 +++ name-based.html 1999/02/14 14:26:49 1.10 @@ -107,15 +107,18 @@ 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