fanf 00/09/13 13:14:50
Modified: htdocs/manual/vhosts name-based.html
Log:
name-based virtual hosts are not new any more -- in fact they are
now the standard way of doing things -- so make the introduction
less anachronistic
Revision Changes Path
1.13 +15 -13 httpd-docs-1.3/htdocs/manual/vhosts/name-based.html
Index: name-based.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/vhosts/name-based.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -u -r1.12 -r1.13
--- name-based.html 2000/09/12 16:32:36 1.12
+++ name-based.html 2000/09/13 20:14:47 1.13
@@ -21,25 +21,29 @@
<H2>Name-based vs. IP-based virtual hosts</H2>
-<P>While the approach with IP-based virtual hosts works very well,
-it is not the most elegant solution, because a dedicated IP address
-is needed for every virtual host and it is hard to implement on some
-machines. The <CODE>HTTP/1.1</CODE> protocol contains a method for the
-server to identify what name it is being addressed as. Apache 1.1 and
-later support this approach as well as the traditional
-IP-address-per-hostname method.</P>
+<P>Early versions of HTTP (like many other protocols, e.g. FTP)
+required a different IP address for each virtual host on the server.
+On some platforms this can limit the number of virtual hosts you can
+run, and because there are concerns about the availability of IP
+addresses it is strongly discouraged by the registraries (ARIN, RIPE,
+and APNIC).</P>
+
+<P>The <CODE>HTTP/1.1</CODE> protocol, and a common extension to
+<CODE>HTTP/1.0</CODE>, includes a method for the server to identify
+what name it is being addressed as. Apache 1.1 and later support this
+approach as well as the old IP-address-per-hostname method.</P>
-<P>The benefits of using the new name-based virtual host support is a
+<P>The benefits of using the name-based virtual hosts is a
practically unlimited number of servers, ease of configuration and use, and
requires no additional hardware or software.
The main disadvantage is that the client must support this part of the
-protocol. The latest versions of most browsers do, but there are still
+protocol. Almost all browsers do, but there are still small numbers of
old browsers in use who do not. This can cause problems, although a possible
solution is addressed below.</P>
-<H2>Using non-IP Virtual Hosts</H2>
+<H2>Using name-based virtual hosts</H2>
-<P>Using the new virtual hosts is quite easy, and superficially looks
+<P>Using name-based virtual hosts is quite easy, and superficially looks
like the old method. The notable difference between IP-based and
name-based virtual host configuration is the
<A HREF="../mod/core.html#namevirtualhost"><CODE>NameVirtualHost</CODE></A>
@@ -51,8 +55,6 @@
<SAMP>111.22.33.44</SAMP>. Then you simply add to one of the Apache
configuration files (most likely <CODE>httpd.conf</CODE> or
<CODE>srm.conf</CODE>) code similar to the following:</P>
-
-
<PRE>
NameVirtualHost 111.22.33.44
Modified: htdocs/manual/vhosts name-based.html
Log:
name-based virtual hosts are not new any more -- in fact they are
now the standard way of doing things -- so make the introduction
less anachronistic
Revision Changes Path
1.13 +15 -13 httpd-docs-1.3/htdocs/manual/vhosts/name-based.html
Index: name-based.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/vhosts/name-based.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -u -r1.12 -r1.13
--- name-based.html 2000/09/12 16:32:36 1.12
+++ name-based.html 2000/09/13 20:14:47 1.13
@@ -21,25 +21,29 @@
<H2>Name-based vs. IP-based virtual hosts</H2>
-<P>While the approach with IP-based virtual hosts works very well,
-it is not the most elegant solution, because a dedicated IP address
-is needed for every virtual host and it is hard to implement on some
-machines. The <CODE>HTTP/1.1</CODE> protocol contains a method for the
-server to identify what name it is being addressed as. Apache 1.1 and
-later support this approach as well as the traditional
-IP-address-per-hostname method.</P>
+<P>Early versions of HTTP (like many other protocols, e.g. FTP)
+required a different IP address for each virtual host on the server.
+On some platforms this can limit the number of virtual hosts you can
+run, and because there are concerns about the availability of IP
+addresses it is strongly discouraged by the registraries (ARIN, RIPE,
+and APNIC).</P>
+
+<P>The <CODE>HTTP/1.1</CODE> protocol, and a common extension to
+<CODE>HTTP/1.0</CODE>, includes a method for the server to identify
+what name it is being addressed as. Apache 1.1 and later support this
+approach as well as the old IP-address-per-hostname method.</P>
-<P>The benefits of using the new name-based virtual host support is a
+<P>The benefits of using the name-based virtual hosts is a
practically unlimited number of servers, ease of configuration and use, and
requires no additional hardware or software.
The main disadvantage is that the client must support this part of the
-protocol. The latest versions of most browsers do, but there are still
+protocol. Almost all browsers do, but there are still small numbers of
old browsers in use who do not. This can cause problems, although a possible
solution is addressed below.</P>
-<H2>Using non-IP Virtual Hosts</H2>
+<H2>Using name-based virtual hosts</H2>
-<P>Using the new virtual hosts is quite easy, and superficially looks
+<P>Using name-based virtual hosts is quite easy, and superficially looks
like the old method. The notable difference between IP-based and
name-based virtual host configuration is the
<A HREF="../mod/core.html#namevirtualhost"><CODE>NameVirtualHost</CODE></A>
@@ -51,8 +55,6 @@
<SAMP>111.22.33.44</SAMP>. Then you simply add to one of the Apache
configuration files (most likely <CODE>httpd.conf</CODE> or
<CODE>srm.conf</CODE>) code similar to the following:</P>
-
-
<PRE>
NameVirtualHost 111.22.33.44