  Rendering server-parsed files using the Mime Types file
You can also configure the Mime Types file to choose which files should be server parsed. Server-parsed files are dynamic web documents (.shtml extension) that are sent to the server before they are displayed by a browser. This is different from static web documents (.html) that are displayed by a browser without passing through the server.
The following diagram illustrates this concept:
 When a browser hits a web site and calls a page, Internet Services sends any non server-parsed files to the browser directly. If there are any server-parsed files that need to be displayed, Internet Services first sends the file to the FirstClass server for processing. After processing is complete, the FirstClass
server sends the file back to Internet Services, which then forwards it onto the browser to display.
Examples of server-parsed files are:
• files with .shtml extensions
• Internet Services web templates
• any documents that include Internet Services script in the code.
Here are examples of MIME type entries for server-parsed files:
• text/x-server-parsed-html TEXT MOSS .shtml
• text/x-server-parsed-html TEXT MOSS .shm
• text/x-server-parsed-html TEXT MOSS .inc
Note
The Macintosh creator code for Netscape is MOSS.
These lines of code identify any html file with extensions .shtml, .shm, or .inc as server-parsed files.
|