Alright, let's all laugh at a semantic argument for a minute...
In accordance with web standards I have opted to not use directory indexes
(which is allowed). As a visitor convenience I use directory overview
pages in their stead. Each directory overview
page is located one level up from where each directory index
would be located, on a page with the same name as the directory...
Again as a convenience to visitors, and to ensure there are no canonicalization issues with search engines, I have chosen to redirect visitors from the directory index
location to the location of the corresponding directory overview
page when they request a directory index
rather than serving them content, a 403 or 404 error at the location they requested, because the overview
pages are essentially the same as the indexes
from a visitor and site usability perspective.
Can I do that? LOL! Sorry, but we're having a really semantic argument about whether there should be a / on the URL from a 'technically correct' POV and I just see some humor in it some times, so IMO each to their own on this one, because it's really a very semantic argument to say they are technically necessary, but as stated previously in this thread, you should know what you are doing before attempting to make a site completely extensionless, because an error can cause linking, image and style sheet location issues.
[edited by: TheMadScientist at 8:15 am (utc) on Apr 28, 2010]