<quote who="[EMAIL PROTECTED]">
> NameVirtualHost does work with a virtual-server modem!
That's because the awkwardly named "virtual server" feature is just port
forwarding. Whether you're doing it with a "virtual server" modem, a nice
switch, a Cisco router or a Linux box, port forwarding is all the same
thing -> no knowledge of the application layer protocol [1] at all (in this
case, HTTP).
> My error was the NameVirtualHost IP specified the external IP. Carefull
> reading of the apache doco following Rick's comments show it ought to be
> the internal IP. And lo and behold it works.
Rather than using an IP at all, I'd suggest doing this:
<VirtualHost *:80>
ServerName www.example.com
...
</VirtualHost>
Then whatever and however you point to it, as long as the Host header is
set, your web server will do the right thing. (Though you can't do this if
you are very specifically serving from a particular IP, perhaps for the
purposes of HTTPS or weird hosting requirements.) This avoids problems you
get with setups such as:
<VirtualHost 1.1.1.1:80> --> static IP configuration, inflexible
<VirtualHost www.example.com:80> --> looks up IP via DNS, flexible, but
involves a DNS look up (many if you have lots of virtual hosts) when you
start your webserver, which can totally suck
For glorious benefit of the archives,
- Jeff
[1] So as not to provoke further crack-addled misinterpretation.
--
linux.conf.au 2007: Sydney, Australia http://lca2007.linux.org.au/
"To do: Start up a a magazine dedicated to picky grammar. Call it 'Whom
Weekly'." - WzDD
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
