This document describes the format of dynamic configuration files, files which you place in your document directories to give the server configuration information.
Web server content is seldom entirely managed by one person. Many times, different parts of a web server are written by different people. For instance, each employee may maintain their own home page.

When these users need to configure something about their directory, it is unrealistic for you as the administrator to allow all of them access to the Netscape Server Manager. In these cases, it is useful to allow them a subset of configuration options so they can control only what they need to.

If you haven't read it already, you should read the form for enabling dynamic configuration files and understand the concepts it describes. You should also configure an area of your server to use these configuration files.


Dynamic configuration files consist of sets of directives which control the server. These sets are surrounded by Files directives which tell the server which files in the configuration file's directory the directives apply to.

<Files PATTERN1>
... directives ...
</Files>

<Files PATTERN2>
... directives ...
</Files>
and so on. PATTERN1 and PATTERN2 are wildcard patterns which tell server which filesystem pathnames to apply the directives they surround to. Any pattern given is first prefixed with the directory containing the configuration file to ensure that it is only applied to subdirectories. There may be as many Files sets in the .nsconfig file as you need.

The file may contain blank lines, and lines which begin with a hash sign (#) will be treated as comments and ignored.

Each directive can take a variable number of parameters. The directives which can appear inside Files regions are: