I was under the impression that /etc/apache2/conf.d/ was for packages to drop their code snips (including vhosts). For example, Cacti, or Nagios3. This would make one of these the default vhost, which is probably not desired in most situations.
I'm definitely remembering this being the case in the past, as that's why they are where they are on my host, but my host has been around for a long long long time. I'm guessing it's no longer policy for packages to drop their code snips in conf.d any longer.
Go ahead and close out bug. Must be an artifact from that this host has been upgraded since the days of an early 2.0 kernel. I have a lots of little issues like this.
Stefan Fritsch wrote:
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. user@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.
-- # Jesse Molina # Mail = jesse@opendreams.net # Page = page-jesse@opendreams.net # Cell = 1.602.323.7608 # Web = http://www.opendreams.net/jesse/