I'm back. The following proved very helpful: At 02:01 PM 10/6/2002 +0100, you wrote:
By removing this I was able to see what was happening. But it leads to some new questions. I was trying to use the RH apache configuration GUI tool. Does anyone actually use this tool for serious work? It doesn't seem to implement control over all apache directives. But if one manually edits the httpd.conf file created by this tool, those edits are lost when the tool is used. Not very nice. The above change, to remove the location directive, is a case in point. Using the RH GUI tool puts it back.A stab in the dark:# # Disable autoindex for the root directory, and present a # default Welcome page if no other index page is present. # <LocationMatch "^/$> Options -Indexes ErrorDocument 403 /error/noindex.html </LocationMatch> This section of configuration may explain your problem. If there is no index.html in your virtual-host, then an index won't be displayed, or a forbidden page: instead you receive "/error/noindex.html" which is the welcome you've got Apache set up page. I disabled this feature by removing the config- as it was more of annoyance than help.
The problem with my virtual hosts not loading was attributable to the GUI tool not putting a DirectoryIndex directive in my virtual host container. I think there is supposed to be a global default for this, but it wasn't correctly specified in the RH modded httpd.conf. All in all, I cannot say I am very impressed with the utility of the RH gui tool so far. Too bad, since I'm just the kind of person this type of tool is presumably designed for: a windows sysadmin looking to use linux on his network.
One last question, should anybody know. There must be a "shadow" copy of the httpd.conf maintained by the RH gui tool somewhere that is read whenever the RH gui tool is loaded. Anybody know where/what it is? I'm wondering if it wouldn't be possible to manually edit that one and have the edits preserved?
-Basil
