jim 98/04/21 15:24:52
Modified: htdocs/manual upgrading_to_1_3.html
htdocs/manual/vhosts details.html
Log:
Some clarification that only one NameVirtualHost
is used per IP:port pair
Revision Changes Path
1.20 +4 -3 apache-1.3/htdocs/manual/upgrading_to_1_3.html
Index: upgrading_to_1_3.html
===================================================================
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/upgrading_to_1_3.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- upgrading_to_1_3.html 1998/04/14 17:27:07 1.19
+++ upgrading_to_1_3.html 1998/04/21 22:24:50 1.20
@@ -91,9 +91,10 @@
<LI>Folks using HTTP/1.1-style virtual hosting will need to list the
ip:port pairs that are supposed to have HTTP/1.1-style virtual hosting
via the <A HREF="mod/core.html#namevirtualhost"><CODE>
- NameVirtualHost</CODE></A> directive. Previously this support was
- given implicitly on the "main server address". Now it has to be
- explicitly listed so as to avoid many problems that users had.
+ NameVirtualHost</CODE></A> directive (one directive per pair).
+ Previously this support was given implicitly on the "main server
+ address". Now it has to be explicitly listed so as to avoid many
+ problems that users had.
Please see the <A HREF="vhosts/index.html">Apache Virtual Host
documentation</A> for further details on configuration.
1.6 +3 -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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- details.html 1998/02/20 06:47:53 1.5
+++ details.html 1998/04/21 22:24:51 1.6
@@ -77,7 +77,9 @@
<CODE>NameVirtualHost</CODE> directive in your configuration file.
<P>Multiple <CODE>NameVirtualHost</CODE> directives can be used each
-with a set of <CODE>VirtualHost</CODE> directives.
+with a set of <CODE>VirtualHost</CODE> directives but only one
+<CODE>NameVirtualHost</CODE> directive should be used for each
+specific IP:port pair.
<P>The ordering of <CODE>NameVirtualHost</CODE> and
<CODE>VirtualHost</CODE> directives is not important which makes the
Modified: htdocs/manual upgrading_to_1_3.html
htdocs/manual/vhosts details.html
Log:
Some clarification that only one NameVirtualHost
is used per IP:port pair
Revision Changes Path
1.20 +4 -3 apache-1.3/htdocs/manual/upgrading_to_1_3.html
Index: upgrading_to_1_3.html
===================================================================
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/upgrading_to_1_3.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- upgrading_to_1_3.html 1998/04/14 17:27:07 1.19
+++ upgrading_to_1_3.html 1998/04/21 22:24:50 1.20
@@ -91,9 +91,10 @@
<LI>Folks using HTTP/1.1-style virtual hosting will need to list the
ip:port pairs that are supposed to have HTTP/1.1-style virtual hosting
via the <A HREF="mod/core.html#namevirtualhost"><CODE>
- NameVirtualHost</CODE></A> directive. Previously this support was
- given implicitly on the "main server address". Now it has to be
- explicitly listed so as to avoid many problems that users had.
+ NameVirtualHost</CODE></A> directive (one directive per pair).
+ Previously this support was given implicitly on the "main server
+ address". Now it has to be explicitly listed so as to avoid many
+ problems that users had.
Please see the <A HREF="vhosts/index.html">Apache Virtual Host
documentation</A> for further details on configuration.
1.6 +3 -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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- details.html 1998/02/20 06:47:53 1.5
+++ details.html 1998/04/21 22:24:51 1.6
@@ -77,7 +77,9 @@
<CODE>NameVirtualHost</CODE> directive in your configuration file.
<P>Multiple <CODE>NameVirtualHost</CODE> directives can be used each
-with a set of <CODE>VirtualHost</CODE> directives.
+with a set of <CODE>VirtualHost</CODE> directives but only one
+<CODE>NameVirtualHost</CODE> directive should be used for each
+specific IP:port pair.
<P>The ordering of <CODE>NameVirtualHost</CODE> and
<CODE>VirtualHost</CODE> directives is not important which makes the