On Monday 19 January 2009, Jesse Molina wrote: > The first vhost found in a system is the default vhost that will be > used if nothing else matches. However, given the current > apache2.conf file, the "default" is not the default at all. > > > u...@host-->grep -v "^#.*" apache2.conf | grep -i include > Include /etc/apache2/mods-enabled/*.load > Include /etc/apache2/mods-enabled/*.conf > Include /etc/apache2/httpd.conf > Include /etc/apache2/ports.conf > Include /etc/apache2/conf.d/ > Include /etc/apache2/sites-enabled/ > > If something is in the httpd.conf file, that will be the default, > but per the apparent directory structure, it's supposed to be in > the sites-enabled directory. There was even an attempt to make the > default load first by prepending zeros to the symlink file. The > problem is that this Include directory is LAST in order, instead of > first.
I think the README.Debian makes it pretty clear that virtual hosts should go into .../sites-enabled/ . Putting them into conf.d is not supported and I don't see any reason to change that. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
