--- Vincent Danen <[EMAIL PROTECTED]> wrote: > What are you talking about? Enabling Indexes by > default somehow makes > Apache work whereas having it off by default > doesn't?
Did it ever occur to you that people use Apache for more than serving websites? Especially desktop users on networks, your primary userbase? I haven't used floppies in all of college, I just stick files in my public_html directory and get them when I need them, I also use my webserver to get files to people I talk to on the 'net. Everybody Apache user I know (that use it on workstations) do the same things. > Apache works just *fine* without Indexes. And > because it is, > potentially, a security hole (through inappropriate > disclosure), the > end user should be forced to enable it where > appropriate... which is > exactly the case. It is not a security hole, and it's a joke calling it one. If someone's gonna put files on a public webserver that they don't want people to get to, they should either have to disable Indexes themselves (I mean geez, this is a very small percentage of Apache users, why punish everybody else?) or use htaccess (which there's much more documentation on). > This has absolutely nothing to do with whether > apache works or not > "out of the box". It absolutely does depending on how you intend to use it. __________________________________________________ Do You Yahoo!? Yahoo! Sports - sign up for Fantasy Baseball http://sports.yahoo.com
