Hi all,

I have a site currently hosted with a company that leases a server from Alabanza. On this server I have to rename any file that I include an SSI call in as .shtml on other servers I am hosted on the file extensions can be anything (.htm, .html, etc) and the ssi call still performs properly.

On a DI server does a file extension have to be .shtml in order to have a ssi excuted properly? What about on a RaQ3?

~ Marcus

On an Alabanza server, you can set it up so the .html files are parsed as well, it's just not the default set up. If your hosting plan includes setting up additional MIME types, all you have to do is add a type as follows:

Type: text/x-server-parsed-html
Extension: .html

This involves the .htaccess file so should not be used if using FrontPage extensions.




------------------
--
Steve Wood
Wood Interactive <A HREF="http://www.woodinteractive.com" TARGET=_blank>www.woodinteractive.com
</A>
Red Hot Hosting www.redhothosting.com (http://www.redhothosting.com)

You specify that yourself, it won't matter what dedicated server providers you go with, they all include Apache. Apache can be configured to


AddType text/html .shtml .shtm
AddHandler server-parsed .shtml .shtm .htm .html


Add this to the Apache configuration file httpd.conf (if you're a dedicated server admin and want to apply it across all virtual servers) OR if you're a customer of a web host, simply create a file called .htaccess in the directory and add the above code.

Hope this has been of some help :)

Be aware that if you do make it so that any file can have SSI extentions, you are wasting CPU processing time. SSI requires that the web server parse the web page for instructions before it feeds the page to the client. The reason it's suggested that only .shtml be parsed is because that way, you have an easy way to denote to the server which files to parse, and which ones not to parse. Parsing all files can unnecessarily bog down the CPU on your server, if you have a busy site.

Of course, this might not matter to you -- just a little info. :)

Originally posted by Tarin:
Be aware that if you do make it so that any file can have SSI extentions, you are wasting CPU processing time. SSI requires that the web server parse the web page for instructions before it feeds the page to the client. The reason it's suggested that only .shtml be parsed is because that way, you have an easy way to denote to the server which files to parse, and which ones not to parse. Parsing all files can unnecessarily bog down the CPU on your server, if you have a busy site.

Yes, that is very true and the reason it's not set up on the Alabanza servers to begin with. That's why it's best to set it up just on the individual domain using the Add Mime Type in the Control Panel (with Alabanza servers) for that particular domain (or manually creating a .htaccess file), rather than setting it up to parse all html files on the server.

Wouldn't it be even better yet to just name the files .shtml when needed and not waste any CPU time unnecessarily? Am I missing something here?