Directory index forbidden by rule

I have a virtual host that won't let me see a particular directory...

I've tried Options Indexes and Options All, but no joy...

Here's the virtual host definition:

# Virtual host www.xxxxxx.com
<VirtualHost *:80>
ErrorLog "/var/log/httpd/xxxx_error_log"
CustomLog logs/xxxx_access_log combined
DocumentRoot /home/www/xxxx/html
ServerAdmin webmaster@xxxx.com
ServerName www.xxxx.com
Options all
<Directory "/home/www/xxxx/html/group">
Options all
AllowOverride none
</Directory>
</VirtualHost>

but it won't let me see a subdirectory.

http://www.xxxx.com/blog/wp-content/

returns a 403 - Forbidden You don't have permission to access
/blog/wp-content/ on this server. Yet I can pull up a file in that
directory just fine.

There aren't any .htaccess files anywhere on the website.

The error logs show:

Directory index forbidden by rule

But there aren't any rules in my httpd.conf file to prohibit this....
The only rule prohibiting access is for the / dir:

#
# 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>

So where do I find the offending rule? Obvously I'm missing something...

TIA

--

Civil Engineer for hire - http://www.seiner.com/engineer.html

use munged address above to email me
SpamTrap DoMeNow@seiner.com

On Mon, 14 Mar 2005 16:54:53 +0100, Davide Bianchi wrote:

> On 2005-03-14, Captain Dondo <yan@NsOeSiPnAeMr.com> wrote:
>> I've tried Options Indexes and Options All, but no joy...
>
> Did you tryed also Options +Indexes?

Yes.

> Is the directory world-executable?

Yes.

Still, no luck.

Any other ideas? I'm stumped.


--

Civil Engineer for hire - http://www.seiner.com/engineer.html

use munged address above to email me
SpamTrap DoMeNow@seiner.com

On Mon, 14 Mar 2005 19:33:43 +0100, Davide Bianchi wrote:
>
> Only some guess: you have somewhere in your httpd.conf or some
> file that is included by it another Options directive that
> superseed the one you added or your Apache is reading another httpd.conf.

Hah! Thanks for pointing out the obvious.

grep -r -C3 Options conf* | less

found

<Directory "/">
Options FollowSymLinks
AllowOverride None
</Directory>

in the non-virtual host section. Changed that to
Options Indexes FollowSymLinks
and all is well....

I'll play with it a bit and specifically allow Indexes only where I want
them but at least I know where the problem is.

:-)


--

Civil Engineer for hire - http://www.seiner.com/engineer.html

use munged address above to email me
SpamTrap DoMeNow@seiner.com