Red Hat Bugzilla – Bug 173012
httpd configuration directory for virtual hosts?
Last modified: 2013-01-09 22:39:48 EST
Description of problem:
I would like to see a httpd configuration directory, which is used only for
virtual hosts, like other distributions have it (as far, as I found while
Personally, I would prefer /etc/httpd/vhosts.d/ like at SuSE/Novell and Gentoo.
This would require a include in delivered httpd.conf and one line more in
At least I didn't find an official suggestion for naming this directory, maybe
you know something better, because you are an Apache guy, aren't you? ;-)
Version-Release number of selected component (if applicable):
Ping...any chance to get this into the httpd 2.2.0 rpm package - and maybe into
Is there any particular reason why the /etc/httpd/conf.d/ directory isn't
suitable? Why add more directories?
I'm looking for a directory only used for virtual hosts where any 3rd party
software could be restricted to (e.g. Confixx-like software). I think keeping
virtual hosts separate from mod_perl, mod_php or mod_python configuration is
reason enough for this.
My thinking is especially then useful, if you've got one file per virtual host
and don't want to search for any configuration file which is not a virtual host
Asked the other way round: Where is the problem to add the directory? Fedora
Core is currently the only big distribution not providing such a IMHO useful
Ping...what's status for FC6?
First of all, I'd not consider this a Blocker bug myself, but that's just my
Second of all, I've been creating /etc/httpd/conf.d/vhost-*.conf files for ages
to achieve the same thing.
But maybe just addding this to the httpd package :
With /etc/httpd/conf.d/vhosts.conf being :
or something like that, would be enough? Other interesting and/or sane defaults
could go into that vhosts.conf file, and could even be commented out by default
in order to keep the current behaviour.
dropping this off the FC6 blocker.
Deciding what is appropriate for the default configuration and what is
appropriate to leave out is often very difficult.
I've never really been convinced there is enough motivation to change the
default configuration like this; I can be swayed each way I try to decide on
what to do with this bug :). "Why not?" is certainly not a sufficient
motivation, nor is "because other distros do it".
My basic objection is that I don't want to get into prescribing config file
layout down to this level; it feels like "policy" where no policy is actually
necessary. Making this change not only means updating the SELinux policy, it
also means changing where system-config-httpd puts vhost definitions, and that
gets this beyond trivial one-line changes.
The fact that we cannot define NameVirtualHost *:80 without also defining a
default *:80 vhost (which is not desirable) means you cannot just drop in new
name-based vhosts into a "vhosts.d", so it would be of restricted utility out of
So on balance my decision on this would be WONTFIX; I hope you can appreciate
that this is not being dismissed out of hand (or worse, out of laziness! :).
*** Bug 232393 has been marked as a duplicate of this bug. ***
*** Bug 246569 has been marked as a duplicate of this bug. ***