You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Daniel Schudel <sc...@penguinpowered.com> on 2000/04/05 22:02:28 UTC

documentation/5961: Clarification of documentation of NameVirtualHost

>Number:         5961
>Category:       documentation
>Synopsis:       Clarification of documentation of NameVirtualHost
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Apr 05 13:10:02 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     schudel@penguinpowered.com
>Release:        1.3.9
>Organization:
apache
>Environment:
N/A
>Description:
The documentation of NameVirtualHost
(see http://www.apache.org/docs/mod/core.html#namevirtual) should be revised.
The value of <addr> that follows the directive is not the "address to which 
your name-based virtual host names resolve".  Rather, it is the IP address of
the physical interface that will receive the requests.  This is important
when a web server handling the request is not the machine which owns the
virutal host name.

Consider the following.  A firewall located at 4.3.0.100 port forwards external 
port 80 traffic to internal server located at 192.168.0.100.
The virtual host to set up resolves it's IP address back to the firewall.
The documentation states that the correct form of the directive would be:
	NameVirtualHost 4.3.0.100
When it actually should be:
	NameVirtualHost 192.168.0.100
>How-To-Repeat:

>Fix:
The relevant portion of NameVirtualHost should be re-written to look like:
With the NameVirtualHost directive you specify the address to which your 
server is bound to (See the BindAddress directive).
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]