To list a directory under httpd on a web server, or not?
Archive - Originally posted on "The Horse's Mouth" - 2006-09-02 21:53:10 - Graham EllisOne of the choices a web server administrator has to make when he configures a web server is what to do with directories in which his content suppliers do not put a home page. Does he want to provide an error response (such as a "404" or "403" page), or does he wish to provide a directory listing?
A directory listing is useful - VERY useful - for developers on test systems as it lets them see what's there and navigate at early testing stages, but conventional wisdom is to turn the faciity OFF on live web servers on the internet and indeed we have it turned off here, even though we also have ensured there's a home page in every directory except one .... exception to be explained in a minute.
To turn indexes off for the whole web site, the web administrator ensures that
Options Indexes
is not specified in his httpd.conf configuration file.
If overrides are allowed for individual directories, the a file called .htaccess can be placed in any directory that SHOULD be allowed to produce an automated index - simply put the Options line I gave above in a file of that name. But why on earth would you want to?
This morning, the postman delivered a heavy weight of papers which I had requested under the Freedom of Information act. A lot of documents to sift, and I've one or two railway-minded friends (this being an issue with the local train service) who wanted to see them rather quickly. So - a new directory on the server, an upload of a .pdf file, and added .htacess and I can simply point them at http://www.wellho.net/dft_foi and they can have a quiet evening reading about whether or not the Bristol to Oxford train should be re-introduced, and how much the Train Operating Company here abouts askes the government to pay to maintain our Melksham service. Oh - there's also a summary here if you don't want to wade through hundreds of pages like I've been doing this afternoon!