iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Configuring the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
7-11
Mapping Requests to Contents
Using Multiple Filemap Directives
If you have a large number of files to make available on your server, it may be useful to
use multiple Filemap directives. Multiple Filemap directives can coexist in the same
configuration file as long as each directive specifies a different matching prefix.
Using multiple
Filemap directives allows you to partition major areas of server content
across different directories or even different disks. For example, given the directives
Filemap /encyclopedia /usr/disk0
Filemap /dictionary /usr/disk7
Filemap /info /G/data1/web
the URL
http://my.server.com/encyclopedia/info/doc.html
will refer to the file
/usr/disk0/info/doc.html
while the URL
http://my.server.com/dictionary/entry/ants.html
will refer to the file
/usr/disk7/entry/ants.html
Handling Directory Accesses
A URL can refer to a directory instead of a specific object. For example:
http://my.server.com:8080/personal/tootie/
When a URL refers to a directory, the server looks for an index file within the directory
being requested. The specific index file the server looks for is determined by the setting
of the
IndexFile directive. For example, if your server receives a directory request,
and the directive
IndexFile index.html welcome.html
is specified in the server configuration file (httpd.config), your server searches first for
the index file index.html within the specified directory. If it finds this file, it returns
the content to the web client. Otherwise, it searches for the specified alternative index
file, welcome.html. If your server cannot find this file, it returns an error message to
the web client (unless automatic indexing is specified; see Enabling Automatic
Directory Indexing on page 7-33).
For complete information on the
IndexFile directive, see Appendix A, Configuration
Directives.