Sun Microsystems Netscape Enterprise Server Administrator's Manual page 177

<Files PATTERN1
... directives ...
</Files
<Files PATTERN2
... directives ...
</Files
PATTERN1 and PATTERN2 are wildcard patterns that tell the server which
filesystem paths to apply the directives to. For example, * would apply the
directive to all filesystem pathnames. Any pattern given is first prefixed with the
directory containing the configuration file to ensure that the directives are
applied only to subdirectories. There can be as many sets of Files directives
in the .nsconfig file as you need.
The file can contain blank lines. Lines beginning with # are treated as
comments. Note that lines are limited to a maximum of 512 characters.
For Windows NT, all paths must use the forward slash (/) instead of the
backwards slash (\), otherwise you receive a server "path not found" error.
Each directive can take a variable number of parameters, all of which must be
lowercase. The Files directives include:
• AddType exp= SHEXP type= mime-type enc= http-encoding
AddType assigns the give type or encoding to the paths represented by the
wildcard pattern SHEXP . One or both of type and encoding can appear,
but only one expression can be used. You cannot apply two MIME types or
encodings to the same pattern of the files.
• ErrorFile reason= error-string code= error-code
path= html-file
ErrorFile causes the HTML file described by the URL suffix path to be
sent in place of the server's default error message. The file is substituted
when an error described by one or both of reason and code occurs.
path is a valid URL to the local server but without the http:// server
prefix. The error codes are the standard HTTP error codes:
• 401 Unauthorized
• 403 Forbidden
• 404 Not found
• 500 Server error
Working with Dynamic Configuration Files
Chapter 7, Configuring Server Preferences 177