Red Hat Bugzilla – Bug 76274
GUI apache configuration tool writes bad DirectoryIndex directive
Last modified: 2015-03-04 20:11:31 EST
Description of Problem:
If I modify the apache config with the GUI tool, hitting http://www.foo.com/
won't work, I have to explicity hit http://www.foo.com/index.html. This is
because the GUI tool writes the following line:
I.e. it doesn't actually give it a value! I had to manually change httpd.conf
for it to work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Nautilus Start Here -> Server Settings -> HTTP Server.
2. Save any changes. In my case I'm using a simple virtual host setup.
3. Use mozilla and go to http://www.yourservername.com/.
You get /var/www/error/noindex.html.
I should get /var/www/html/yourservername.com/index.html. (That's where I put
my doc root.)
Manually changing DirectoryIndex to say index.html works fine. However, the GUI
tools is really quite nice, and it'd be great if this simple fix were made.
Also, if anyone cares to say... where does the GUI tool get its httpd.conf
template? It would be nice to be able to modify that, for the options it can't
I can verify this as true. Upgraded to 8.0 and my old httpd.conf was no longer
valid. The redhat-config-httpd tool builds a config file where the
DirectoryIndex directive is empty, resulting in all http accesses to the system
returning the default test page. The problem only manifests itself when you
create a virtual host other than the default one. Should be an easy fix. Adding
the entry that email@example.com mentioned cures the problem. (Note: I think the
apache config tool's data lives in /etc/alchemist/namespace/apache but I don't
know if that is true or not)
The files in /etc/alchemist/namespace/apache are binary files, and it would seem
are not editable. I did find /usr/share/apacheconf/httpd.conf.xsl which appears
to be a httpd.conf file wrapped in what I believe is XML. Maybe that is the
file used by redhat-config-httpd for its default values. It would be nice to
know for sure.
OK, i've checked with the latest version that'll be out via rawhide real soon
now and there it works nicely.
Concerning the question about the template file, thats "fairly" simple: r-c-h
uses internally a XML representation of the configuration. Parsing a httpd.conf
file was out of the question when we designed the tool quite some time ago as
it's really a mess to parse correctly.
So all configuration things are stored in
where you can find a local.adl and a rpm.adl (btw, the alchemist is our XML
backend software). The rpm.adl contains the 'default' setup which we ship and
which is used as a basis for the configuration. All local changes are stored in
local.adl. Both files are gziped XML files so can be manually edited.
From the final XML configuration the httpd.conf file is generated using the Xslt
Processor of 4Suite. The xslt file for the configuration can be found here:
It uses only fairly simple Xslt style things as anything else gets fairly messy
Thats about it. Just in case you wondered how r-c-h creates the config file. :-)
Read ya, Phil