That's a good question. I'm not sure what is the right answer to your question. I'll do some research and get back to you if I find an good answer. You should email the people at iPage as they probably could answer your iPage question..
That is true creative, but Ian is saying that this server is setup so it parses all .htm and .html files as SSI, which could be bad if they have a lot of users on the netowrk that don't want it...
There is no need to parse pages which contain no SSI as this generates an unnecessary overhead. Therefore it is often conducive to separate your .html from your .shtml pages. If, of course, all your pages do require SSI then I can see the benefit of having .html pages parsed by the server also. On Apache the Directive that controls which extensions are parsed and which are not is.
Simply add the .html extension to the server-parsed line..
In answer to the original question. You can have any page as a default (like index.html) by amending the server's configuration file. On an Apache server the file is named httpd.conf, and the directive looks like this:.
Just append the index.shtml (or whatever page you want as a default) to the DirectoryIndex line, that should do it...
I guess you could add that to a htaccess file if you don't have control of the http.conf file...
Well, to answer his question,.
Im pretty sure that itll take all,.
Index.html, index.htm, index.shtml, index.shtm, index.cfm, and even default.html, etc etc .....
I use SSI on ALL my pages (.
)that I'm creating for a friend's business ... works like a charm ... (right now it's new.shtml as I'm still creating right nowhehe )..
And on IIS you can set up multiple pages, and what order to parse them in... such as:.
And so on. I agree with torrent 100% on NOT using the ssi parser as a default (on every page) unless nearly every page uses ssi's. Same thing for my coldfusion pages. I don't save in .cfm unless I have some server side code in the page (though about 99% of them do)..
The real plus I can see is increased server speed, decreased server load, and for me... I can use both coldfusion and asp in the same website/ application with no changes whatsoever...
I think you got a little confused about what I was meaning (unless I'm reading you wrong)..
All of A1 runs as .html pages. In these .html pages there are .html includes (such things as a common menu, header, advertising area, etc. such as <!#include virtual="/ssi/navigation.html" > which allows me to change my entire navigation area from one template. However, inside one of my .html includes, I can run a .txt include or even execute .cgi includes <!#include virtual="/random.cgi" > for displaying random links for example..
What I was saying, is that you do not.
To have your page extension as .shtml in order to run server side includes...
Ian, html alone cannot parse includes. the server has to know they are there and for it to do it it has to be shtml. other than that your server has permission to parse everything as SSI so you won't need the shtml extension..
That's what torrent was spitting out...