I have a site built with static html files and I need to add a segment of markup to every page. The natural choice to accomplish this is to use server-side includes (SSI).
The SSI handler does not map to .html files by default, so I'm left with 2 choices:
- Rename all files to .shtml, which requires replacing all links.
- Map the SSI handler to .html files. (I'd like to make this change quick and dirty, so this is my preferred option.)
Is there any major issue with mapping the SSI handler to .html files? This is not a high-traffic site by any means, so performance should not be a concern.
Best Answer
There aren't any concern to your option 2 for a non high-traffic site. The HTML will still render as normal HTML, but it will also process the SSI.
As a side, is there a reason why you would use SSI instead of a full scripting solution like ASP.NET, PHP or even Classic ASP? SSI lived a great life, about a decade ago.