On 2007-02-16, forrie@gmail.com <forrie@gmail.com> wrote:
> Okay, I'll see if I can test that.

See if you can also improve your quoting... is really hard to figure
out to what or who you're responding...

> However, if I got directly to the host with the IP address, shouldn't
> it go to the VirtualHost that the ServerName is the hostname for?

....hu?

> Meaning, the host is named "machine1"

the hostname doesn't matter if you're using VHosts. And if you aren't
then it matter a little.

> How can I reliably test this without the host header... perhaps on the
> command line.

he... unless you can craft a complete http request is quite hard. The
simplest way is to use a browser, even lynx will do.

><VirtualHost *:80>
>
> with
>
><VirtualHost machine.name.com:80>

The *:80 or machine.name.com:80 is the same thing you have in the
NameVirtualHost directive, this is to allow multiple NameVirtualHost
with different port/ip number to be served by the same machine without
confusion.

Davide

--
Slight disorientation after prolonged system uptime is normal for new Linux
users. Please do not adjust your browser.
-- From a Slashdot.org post