Red Hat Bugzilla – Bug 246569
Ship vh.d directory for virtual host configuration
Last modified: 2007-11-30 17:12:09 EST
Description of problem:
It would be useful to have a /etc/httpd/vh.d directory where one could configure
virtual hosts, similar to the way modules are configured in conf.d. This
configuration after all other configuration directives (i.e. main and module
specific) have been applied, making sure all VHs inherit everything properly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is an enhancement request, obviuosly.
Created attachment 158405 [details]
Created attachment 158406 [details]
Configuration file patch
Created attachment 158407 [details]
README file for vh.d directory
Created attachment 158408 [details]
Spec file patch for conevenience
Sorry, the sentence should read:
This configuration would occur after all [...]
The benefit of this approach, which I failed to mention, is that default
httpd.conf can be delivered over RPM upgrades, therefore making deployment of
new defaults easier (i.e. no need for admins to merge .rpmnew stuff into the
Thanks a lot for the hard work and patches - but (there's always a but :)... see
bug 173012 for the rationale why I don't think this is a good idea.
*** This bug has been marked as a duplicate of 173012 ***
That's cool - it's not a big deal for me to add this one line to the back of
httpd.conf. I was just lazy and wanted to avoid editing httpd.conf every time I
upgrade my Fedora/EL boxes. It's also kind of cool to get defaults by default ;-)
Related to the rationale from bug #173012, this problem:
"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
is trivially fixed by having a .conf file in vh.d (or whatever it's called) that
is alphabetically before anything else (e.g. starting with _), which then
includes user specified NameVirtualHost directive (and any other user-overriden
global directives), without the need for httpd.conf (or anything in conf.d) to
carry that. This can be mentioned in the vh.d/README.
SELinux thing isn't a big deal. Policy changes all the time.
I do get the point about system-config-httpd. This would need to be fixed for
something like this to work properly. Although I'm not a Python guy, it would
probably be good fun... :-)
Anyhow, if my persuasion isn't working (i.e. you still think this falls under
"why not"), feel free to leave WONTFIX - it's really not a big deal.