After circling back around to this today, I found the cause. The
welcome.conf file in /etc/httpd/conf.d contains the following:
#
# This configuration file enables the default "Welcome"
# page if there is no default index page present for
# the root URL. To disable the Welcome page, comment
# out all the lines below.
#
<LocationMatch "^/+$">
Options -Indexes
ErrorDocument 403 /error/noindex.html
</LocationMatch>
Not only does this counteract any Index overrides you have made for the root
dir, but it also points the 403 handler to a file that doesn't exist.
Commenting out the LocationMatch took care of my issue.
James
> -----Original Message-----
> From: [email protected] [mailto:blueonyx-
> [email protected]] On Behalf Of James
> Sent: Thursday, July 22, 2010 11:15 PM
> To: 'BlueOnyx General Mailing List'
> Subject: [BlueOnyx:05094] Re: Overriding Indexes in web root
>
> That's what I'm saying - I did change the appropriate settings to allow
> Override of Indexes (I even tried allowing override of everything in
> there).
> The thing is - with the override set in the main root web directory, it
> actually takes effect in all the subdirectories from there. I haven't
> seen
> anything that makes sense to me why it skips the root. Without the
> override
> in my .htaccess, the subdirectories also give the access denied. So,
> it's
> obviously taking my override and applying it, but why does it start one
> level below the web root?
>
> thanks
>
> > -----Original Message-----
> > From: [email protected] [mailto:blueonyx-
> > [email protected]] On Behalf Of Michael Stauber
> > Sent: Thursday, July 22, 2010 6:49 PM
> > To: BlueOnyx General Mailing List
> > Subject: [BlueOnyx:05091] Re: Overriding Indexes in web root
> >
> > Hi James,
> >
> > > I'm sure I'm just overlooking something here, but it's driving me
> > nuts. Is
> > > there a configuration setting somewhere that is specifically
> > preventing
> > > Indexes from working in the root web directory for any site? I
> have
> > my
> > > server set up so that Indexes can be overridden, and I put an
> > .htaccess
> > > entry of "Options +Indexes". When I go to http://www.mysite.com/,
> I
> > get a
> > > 403 trying to access and a log entry of "Directory index forbidden
> by
> > > Options directive: /home/.sites/XX/siteX/web/".
> >
> > In the BlueOnyx GUI go to "Server Management" / "Network Services" /
> > "Web".
> > That allows you to configure which Options are allowed for web
> > directories and
> > AllowOverride settings are allowed in .htaccess files.
> >
> > By default we don't want people to be able to override certain Apache
> > settings
> > with .htaccess files, as that could be potentially dangerous.
> >
> > So check your settings there and adjust them accordingly.
> >
> > --
> > With best regards
> >
> > Michael Stauber
> > _______________________________________________
> > Blueonyx mailing list
> > [email protected]
> > http://www.blueonyx.it/mailman/listinfo/blueonyx
>
> _______________________________________________
> Blueonyx mailing list
> [email protected]
> http://www.blueonyx.it/mailman/listinfo/blueonyx
_______________________________________________
Blueonyx mailing list
[email protected]
http://www.blueonyx.it/mailman/listinfo/blueonyx
