index.html
, but most modern HTTP servers offer a configurable list of filenames that the server can use as an index. If a server is configured to support server-side scripting, the list will usually include entries allowing dynamic content to be used as the index page (e.g. index.php
, index.shtml
, index.jsp
, default.asp
) even though it may be more appropriate to still specify the HTML output (index.html.php
or index.html.aspx
), as this should not be taken for granted. An example is the popular open source web server Apache, where the list of filenames is controlled by the DirectoryIndex
[1] directive in the main server configuration file or in the configuration file for that directory. It is possible to make do without file extensions at all, and be neutral to content delivery methods, and set the server to automatically pick the best file through content negotiation.index.html
, but most modern HTTP servers offer a configurable list of filenames that the server can use as an index. If a server is configured to support server-side scripting, the list will usually include entries allowing dynamic content to be used as the index page (e.g. index.php
, index.shtml
, index.jsp
, default.asp
) even though it may be more appropriate to still specify the HTML output (index.html.php
or index.html.aspx
), as this should not be taken for granted. An example is the popular open source web server Apache, where the list of filenames is controlled by the DirectoryIndex
[1] directive in the main server configuration file or in the configuration file for that directory. It is possible to make do without file extensions at all, and be neutral to content delivery methods, and set the server to automatically pick the best file through content negotiation.