Hi Ovid,

<verbose>

If you want to intercept calls to HTML files, I think there are probably two ways of doing this.

1. Create an ISAPI filter - I think this would have to be written in C or VB or something. I haven't done this but I know MS have a few samples you can download. - I think this would take a lot of time to develop so it might not be worth it for just one site
2. You could create a new Script Mapping in IIS for .html files. Instead of letting IIS feed the html straight to the browser you could create a parser script (say it's called 'stripSSI.pl') and create a script mapping pointing to perl path/to/stripSSI.pl %s - you would need to play around with that path - I haven't done this before so it might need to be different. stripSSI.pl could then clean up the SSI and handle the template tags directly.

To create a script mapping in IIS [4|5], go to the website properties, click "Home Directory" Tab -> Configuration.

You might also want to think of other ways of letting the client update HTML. It would depend on what sort of changes the client would be making and how often. One option would be to let the client upload to a 'build' subfolder with a few home-grown tags, then let them run a script which checks which filed have changed, then fills in your home-grown tags.

</verbose>

$code or die
$ perldoc perldoc