Question about Server Side Includes under IIS [more inside].
I've got a bunch of files that include Server Side Include directives supported by Apache. Unfortunately, many of them, such as #set and if-then-else logic are not supported by Microsoft's IIS, which I am now running. My question is, is it possible to take Apache's
mod_include.c, compile it into a .dll, and use that to process .shtm, .shtml, and .stm files instead of ssinc.dll? Is this a really, really, really bad idea? Has someone figured out a way around this that will work using a similar approach?
There is
a page on Apache's website that describes the process of compiling a module into a .dll, but I'm a bit confused on what needs to be done as I typically don't do much besides Perl/SQL.
If you're set on using IIS, it would probably be easier to simply edit the files to use the ASP syntax, and then configure IIS to use the ASP filter to process .shtml etc. files.
posted by kindall at 1:40 PM on May 7, 2004