iTP Secure WebServer System Administrators Guide (Version 7.5+)

text/x-server-parsed-html to identify files to be parsed. To tell the server which extension
you want to correspond to these files, you specify the MimeType directive in the mime-types.config
file. For example, the server default is:
MimeType text/x-server-parsed-html shtml
This directive marks for parsing any file ending in .shtml.
The default MIME-type extensions specified in the mime-types.config file are lowercase.
Therefore, if you have a file with the extension .SHTML, this file appears as text unless you add
SHTML as an extension to the appropriate MimeType directive or Region command. See
“MimeType” (page 224).
Alternatively, if you are not concerned about the negative performance impact of having all.html
files parsed, you could use:
MimeType text/x-server-parsed-html html
This directive causes the server to parse all.html files searching for SSIs. Server parsing also can
be specified by CGI programs that return a Content-type: text/x-server-parsed-html
header.
SSI Directives
All SSI directives to the server are formatted as HTML comments. Each SSI directive has this format:
<!--#command [[tag1="value1" [tag2="value2"] ...] -->
where command is one of these:
config
controls various aspects of file parsing. This command accepts three tags:
errmsg
controls which message is sent back to the Web client if an error occurs while a
document is being parsed. When an error occurs, it is logged in the server’s error
and extended logs, in addition to being returned to the Web client. For example:
<!--#config errmsg="The server cannot satisfy request"-->
The default behavior of the server is to return error messages formatted as SGML
comments. If you use the configuration errmsg directive, the text of errmsg is
returned to the Web client as is, it is returned within a comment only if you specify
it explicitly. For example:
errmsg="<--!this is an error message -->""
timefmt
gives the server a new format to use when providing dates. This string is compatible
with the strftime library call under most versions of UNIX. For example:
<!--#config timefmt="%A"-->
the day is: <!--#echo var="DATE_LOCAL"--><br>
<!--#configtimefmt="%Y"-->
the year is: <!--#echo var="DATE_LOCAL"--><br>
<!--#config timefmt=%T"-->
the time is: <!--#echo var="DATE_LOCAL"--><br>
<!--#config timefmt="-->
the default string is:<!--#echo var="DATE_LOCAL"-->
Output:
the day is: Wednesday
the year is: 1996
the time is: 14:21:34
the default string is: Wednesday, 31-Jan-96 14:21:34 EST
The strftime(3) - "%z" (time zone) conversion specification forces the local time zone
to be inserted into the output time string. Using strftime(3) is not desirable if the time
being echoed is DATE_GMT.
Setting Up Clickable Images 131