Notes on Server-Side Scripting
When I wrote this page I was looking at handling server errors by using Server-Side processing. In particular it was providing an interactive response to a 404 - page not found error. I wanted to write a script that would guide the visitor to a page that was similat to the one that they were looking for.
SSI and CGI Scripts are fsar more than what I first presented. I had not well explaned the page.
The Wikipedia explanation
Server Side Includes (SSI) is a simple interpreted server-side scripting language used almost exclusively for the World Wide Web. It is most useful for including the contents of one or more files into a web page on a web server (see below), using its #include directive. This could commonly be a common piece of code throughout a site, such as a page header, a page footer and a navigation menu. SSI also contains control directives for conditional features and directives for calling external programs. It is supported by Apache, LiteSpeed, nginx, IIS as well as W3C's Jigsaw.[1] It has its roots in NCSA HTTPd.[2]
In order for a web server to recognize an SSI-enabled HTML file and therefore carry out these instructions, either the filename should end with a special extension, by default .shtml, .stm, .shtm, or, if the server is configured to allow this, set the execution bit of the file.[3]
Server Side Includes
One of the ways that you can handle server errors is to use a CGI script (Server-Side Include) running on
your webserver. To do this you will have to have the CGI module activated and available to you.
Top
SSI (Server Side Includes) are directives that are placed in HTML pages, and evaluated on the server while the pages are
being served. They let you add dynamically generated content to an existing HTML page,
without having to serve the entire page via a CGI program, or other dynamic technology.