Dead-Lands

trying to set this up, and I want visitors to be able to see the file structure, yet whenver I go to the address I either get the welcome page with no ability to browse to folders, or if I put an index.htm in there, that instead.

I think it's got to do with permissions somewhere but I can't find where. Anyone have any experience with Apache that has wanted to do this (most of the time you want this disabled, so I suspect it's disabled by default, just can't find where)

Throw this into your htaccess file:

Options +Indexes

just to be clear, where is my .htaccess normally supposed to reside?
yes I am that much of a noob.

my docs are /var/www/html if that helps, and this is on a fedora system

Should be somewhere in your apache configuration directory. If memory serves, that should be /etc/httpd or /etc/apache.

Though, keep in mind, sometimes the htaccess materials are declared in-line in your apache configuration.

hmm well when I put that in the .htaccess I get an Internal Server Error (500), remove the .htaccess and it's back to how it was.

So I want to password protect this directory, so I put in the httpd.conf AllowOverride AuthConfig for the "/var/www/html" directory, and then put the following in an .htaccess file:



and then edit/create the .htpasswd with:


and I get a 500 error, if I remove the .htaccess I load just the index.html file

If I change my conf to :


same 500
If I remove eveything but the Options +Indexes then it works for listing the directorys but no pass protect

grrr figured it out, my htaccess is now:


It was the last line that was killing me, going to change the AllowOverride option back to AuthConfig and make sure this is working right.

So if I change the AllowOverride option in my httpd.conf to AuthConfig I get 500 errors, if I change it to All I get the login prompt at the specified directory with the .htaccess and .htpasswd.

So my question is, what does having AllowOverride set to All really do, and why does AuthConfig not work?