Forum Moderators: open
in addition, "index.html" per se is meaningless in the url (there is no keyword there), exposes your technology, and makes the url less flexible for future technology changes.
the general purpose of the index.html document is to be the "default" document for displaying the contents of a directory.
to me "default" means you don't have to specify it.
on the other hand, apache makes it possible to fix this:
how to remove index.html from the URL [webmasterworld.com]
IIS7 has a URL Rewrite Module [learn.iis.net], or you can parse all requests in IIS6 (wildcard handler mapping) or in IIS7 (integrated pipeline mode) as ASP.NET requests, and use its built-in URL rewriting facilities and/or the UrlRewritingNet.UrlRewrite [urlrewriting.net] module.
i had always suspected iis was fundamentally flawed but now that i have looked under the covers i am certain of it.
I've done a lot of IIS in the past and I agree ;) IIS7 is the first half-decent version of IIS imho.
So although the URL "/" is serviced by the file "/index.html", you should be able to independently change things so that the URL "/index.html" is not serviced by a file but instead returns a redirect to a different URL, such as "/".
Apache does allow that. Simply,
RewriteRule..[1]<snip>[/1]..[R=301,L] enables the redirect to a different URL when the URL "/index.html" is requested, and DirectoryIndex associates the URL request "/" with the right file, such as '/index.html', on the server.