On 08/07/2014 05:16 PM, M Busche wrote:
Frank,
I don't think you understood what I was trying to say. My complaint
was that in the pre-packaged configuration made with the ubuntu
distribution, the default vhost configuration is placed in a file
prefixed with the string 000 which causes it
Frank,
I don't think you understood what I was trying to say. My complaint was that
in the pre-packaged configuration made with the ubuntu distribution, the
default vhost configuration is placed in a file prefixed with the string 000
which causes it to be loaded first. I renamed it to have a
Hi,
I notice that the default virtual host configuration file name is
000-default.conf. I presume the convention of starting virtual host
configuration file names with a three digit number governs the order in which
the configurations are applied. Can someone point me to the apache docs web
On Wed, Aug 6, 2014 at 5:20 AM, M Busche spammymat...@yahoo.com.invalid wrote:
Hi,
I notice that the default virtual host configuration file name is
000-default.conf. I presume the convention of starting virtual host
configuration file names with a three digit number governs the order in
Ooops! Somehow I missed the in alphabetical order the first time I read
that. Thanks for making me read that again!
After playing with this last night, it looks to me like Apache stops as soon as
it finds a virtual host with a matching ServerName (or ServerAlias). In my
case I have two
Bad idea. Use the default vhost behaviour to define what vhost will be used
for unknown hostnames not matching any ServerName / ServerAlias directive.
The default *:80 vhost must be defined first.
You can even use ServerName ip or ServerName random hostname in the
default vhost.
Frank
On Wed,
