How to set up IIS for SSI

[SpecSys]

I am moving a couple of web site from an external host to our internal windows 2000 sbs. I noticed that none of my #include features work anymore and I am wondering if there is something I need to set up in the IIS web properties to allow this.

 

[Willy2782]

Can you mention what fetures...

 

[SpecSys]

I am not sure what you mean by features...Basically I have a left side menu and footer which are the same per each page and written into the html with #include. Worked fine on the outside host server, but our newly installed SBS doesn't recognize and include the menu. How do I set up server side scripting on it including #include and also, cgi.

 

[cian]

What servers are you using?

SSI normally runs on Apache, right? And some others too I presume?

Just a guess as I have never done this and don't know if you can but can you create a .htaccess file, then tell the server to parse the documents for SSI, check here for details:

http://www.bignosebird.com/sdocs/enable.shtml

or

http://www.oreilly.com/info/cgi/ch05.html#config

As for CGI try the Apache or CGI forums.
This might help

http://hoohoo.ncsa.uiuc.edu/docs/tutorials/cgi.html

Nollaig shona agus athbhliain faoi mhaise daoibh.
::

http://www.endamcg.com

 

[SpecSys]

Thanks for the advice guys, but I figured it out. I need to add the extension .html to the list of executable extensions under the configuration tab and then point it to a file ssinc.dll in the System32/Inetsrv folder.

 

[cian]

Does this mean your server will parse all .html documents?
I presume then you will use .htm for all other documents cos getting the server to parse ALL docs is not a good idea. AFAIK.
Just 2cents

É
::

http://www.endamcg.com

 

[SpecSys]

Not sure what you mean cian...all webpages on the site have the same menu and header which need to be called through the #include command. There are only about 30 pages on the whole site. I guess I am just not sure what you are referring to..I'm not that familiar with it.

 

[Wullie]

Hi mate,

Check out faq65-1948

That FAQ is for Apache but realates to any server.

Hope this helps Wullie

http://www.freshlookdesign.co.uk

http://www.freshlookdesign.com

http://www.mailtosanta.co.uk

The pessimist complains about the wind. The optimist expects it to change.
The leader adjusts the sails. - John Maxwell

 

[cian]

The FAQ Wullie posted explains it very well but basically:

Any document using SSIncludes needs to be processed by a server.
If ALL documents are processed by the server then it makes the server have to work very hard to do this. Only files which need to be processed should actually be processed.

Example, my server processes files with the standard .shtml and only these files. Which means my 30-40 other documents with a .htm extension will not get processed and therefore it puts less strain on the server.

If all your 30 pages uses SSI then they will need to be parsed. But if you have an additional 10-20-30 documents which don't need to be parsed then you should separate them by using a different extension.

Does that make any sense?

É
::

http://www.endamcg.com

 

[SpecSys]

Yes that does make sense, thankyou.

By "other documents" you mean pages on the defined website, correct. Not something stupid like all files onthe entire machine? That sounds dumb to ask, but just want to be sure.

 

[Wullie]

Hi mate,

If you have defined this and not explicitely stated that it is only for this domain, it will affect every single html file on the entire server.

Hope this helps Wullie

http://www.freshlookdesign.co.uk

http://www.freshlookdesign.com

http://www.mailtosanta.co.uk

The pessimist complains about the wind. The optimist expects it to change.
The leader adjusts the sails. - John Maxwell