Mark A. Craig wrote:
Sorry I got the sense of things backwards earlier. Isn't there
another more brute-force option, to simply place an empty index.htm
file in every directory that shouldn't be browsed? Doesn't the
presence of an index file disable browsing even when it's enabled in
principle for that directory? The open source blog software I use
in fact came pre-packaged that way, with index files placed in all
the directories where browsing wasn't desirable.
Mark
---------------- End original message. ---------------------
Sure, that will work. But it relies on the presence of that file and
that is a potential security hole if somebody forgets to include it
or deletes it thinking it is not needed.
Personally, I think fixing it in the configuration file is a better way to go.
Dragon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
