>One thing I learned is that Apache can have problems figuring out which virtual host to use in some cases:
>>If no ServerName is specified, then the server attempts to deduce the hostname by performing a reverse lookup on the IP address.
ServerName is the name Apache reports in Error messages and using for redirects. It has nothing to do with the Host-Header sent by the client. If it did, a reverse lookup definitely wouldn't be of any help either.
His remedy was still ok though - just for the wrong reasons.
I'm the author of the post linked above: thanks for the clarification about ServerName. I spent a lot of time reading that documentation and got pretty confused about how it was actually being used.
Complementing it, when there is no Host HTTP header, apache displays the default virtual server for the port used. Unless you've set it, it's the first entry on your config file.
It's not a nitpick. It's the difference between making stuff up and reading the documentation. It does matter when reason about how to configure your server.
>One thing I learned is that Apache can have problems figuring out which virtual host to use in some cases:
>>If no ServerName is specified, then the server attempts to deduce the hostname by performing a reverse lookup on the IP address.
ServerName is the name Apache reports in Error messages and using for redirects. It has nothing to do with the Host-Header sent by the client. If it did, a reverse lookup definitely wouldn't be of any help either.
His remedy was still ok though - just for the wrong reasons.