ISP supports SSI but not index.shtml?

[littlegiant]

Is there any reason why an ISP would support SSI but would not want to support index.shtml files? Assuming they're using Apache, it seems to me all they would have to do is add index.shtml to the DirectoryIndex directive in their httpd.conf file. Before I call the system administrator tomorrow and ask him, I was just wondering if there was something I overlooked.

If anyone has some quick info on this, I would sure appreciate it. Thanks.

(edit)

Okay, my bad. Disregard this post (unless you have a further comment). I didn't know that a server could be configured to run SSI on web pages carrying the .htm or .html extension.

[cyanide]

That does seem pretty odd...

You can actually make modifications in an .htaccess file.
Alot of directives that reside in httpd.conf can me modified via an .htaccess file.

For modifying the extension, you can put this

DirectoryIndex index.shtml default.htm index.html
The server will look for the index file in the order it is shown here

[littlegiant]

Yes thanks for the response. I was reluctant to call my system adminstrator because he gave me a great deal on my webhosting package (on account of I'm such a good customer) so I didn't really want to pester him with alot of questions.

I knew about the DirectoryIndex line but I also figured out (after mucking about with my home development server) that you can modify the "AddOutputFilter INCLUDES" line to include not only .shtml files but also .htm and .html files. So I figure that's what my ISP has done. They've excluded index.shtml from the DirectoryIndex but they've enabled SSI to be run on .htm and .html files (which is okay by me).