Originally posted by Cool_Hand_Luke
So I tried the above,
nothing is here now..... should there be?
Yes, there should be something there else there is no need for the "Directory" directive. I posted that directive only as an example if you're using it. The "Directory" directive is used to set settings for specific directories. You'd have one for the root of your site and then you'd use others to add or change things on a directory by directory basis, if you need to. For instance, I disallow all access to the root of my site by default:
Deny from all
So then I'd use it to allow access to one of the virtualhosts:
Allow from all
Now anyone can access anything under that website. But then I have another directory where I want to list files vs load an index.html, so I add a few mod_autoindex options for that directory that I want to use:
Options Indexes FollowSymlinks
Anyway, I simply meant to not add the "/" at the end for those directives. That's all. The manual states the following:
There appears to be a bug in mod_dir which causes problems when the DocumentRoot has a trailing slash (i.e., "DocumentRoot /usr/web/") so please avoid that.
But yes, as stickman stated, you need to make sure that mod_dir is loaded for the redirects to work correctly. It usually is in most default httpd.conf files. Also, you should probably run "/path/to/httpd -t" to test your configuration after making changes, as well.