Mailing List Archive

slive 00/09/15 12:09:47

Modified: htdocs/manual/mod core.html
Log:
PR: 5961

Go into excessive detail about how to handle NameVirtualHost for
boxes behind a NAT device. (Yes, indeed, there seem to be plenty
of people smart enough to configure a firewall, but not smart
enough to figure this one out.)

Revision Changes Path
1.172 +9 -3 httpd-docs-1.3/htdocs/manual/mod/core.html

Index: core.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/core.html,v
retrieving revision 1.171
retrieving revision 1.172
diff -u -r1.171 -r1.172
--- core.html 2000/09/12 16:32:35 1.171
+++ core.html 2000/09/15 19:09:47 1.172
@@ -2132,9 +2132,15 @@

<BLOCKQUOTE><CODE>NameVirtualHost 111.22.33.44</CODE></BLOCKQUOTE>

-With the NameVirtualHost directive you specify the address to which your
-name-based virtual host names resolve. If you have multiple name-based
-hosts on multiple addresses, repeat the directive for each address.<P>
+With the NameVirtualHost directive you specify the IP address on which
+the server will receive requests for the name-based virtual hosts.
+This will usually be the address to which your name-based virtual host
+names resolve. In cases where a firewall or other proxy receives the
+requests and forwards them on a different IP address to the server,
+you must specify the IP address of the physical interface on the
+machine which will be servicing the requests. If you have multiple
+name-based hosts on multiple addresses, repeat the directive for each
+address.<P>

Note: the "main server" and any _default_ servers will <STRONG>never</STRONG>
be served for a request to a NameVirtualHost IP Address (unless for some