Indexes: directories with restricted content not listed anymore?
Posted on 2004-04-05
My ISP has upgraded the server hosting one of my websites. On the new server, the version of Apache is 2.0.46 (on the old one it was 1.3 I think). There may also be a different httpd.conf file --which I don't have access to.
Before the change, directories with subdirectories would be indexed completely, including the subdirectories with forbidden access (however, trying to click on one of those would give a "Forbidden" error). In the new setup, only those subdirectories that can be explored are listed.
For example, assume 3 directories:
I want both users "foo" and "bar" to see the index of store/ (which is "Parent dir", "foo" and "bar"). Of course, user "foo" can not go *into* directory store/bar, and vice-versa "bar" cannot go into store/foo, but both "foo" and "bar" have complete listing access to store.
I have appropriate .htgroup and .htpasswd files defining access and group membership of users foo and bar. Then, I have an .htaccess file per directory:
AuthName "Store areas"
AuthName "Private area for Foo"
Require group foo
AuthName "Private area for Bar"
Require group bar
With the previous setup, everything was fine (both foo and bar could see the entire index of store, but go only in their own directory). Now, only the directory(ies) they have access to are listed by mod_index. Is there some Apache variable that may be set differently by my ISP, or is it just the different version of Apache that caused this? In any case, How can I get back to the previous behavior with Apache2.0?