iTP Secure WebServer System Administrators Guide (Version 7.5+)

../26-Mar-9510:14
CVS/17-Mar-9513:44
a-very-long-file-name-test17-Mar-9512:OK
size-100000.html17-Mar-9512:1597K
subdir/17-Mar-9513:44
test.html17-Mar-9512:15OK
Automatic directory indexing is disabled by default. If no index file is available, the server returns
an error for any attempt to access a directory.
For more information about the DirectoryIndex command, see “Region” (page 232).
Disabling Logging
You can disable logging for specific requests. When you disable logging for a request, no entry
is generated for that request in the server log files. This feature is useful for omitting unimportant
log entries. For example, you could disable logging for requests coming from your own company,
or you could disable logging for requests corresponding to a particular region.
To disable logging for specific requests, you can use the NoLog command in a Region directive
as:
NoLog [pattern pattern ...]
where:
pattern
specifies one or more client host names or IP addresses. If a Web client host name
or IP address matches one of the specified patterns, logging is disabled for all
requests corresponding to the relevant region. If no patterns are specified, logging
is disabled for all requests corresponding to the relevant region.
For example, if your company domain is wonka.com, you could use this directive
to disable logging for all requests from within your company:
Region * {
NoLog *.wonka.com
}
To disable logging for requests affecting only files that have the .gif extension,
you would specify:
Region *.gif {
NoLog
}
Using the NoLog command with a host name only works if there is Domain Name Server (DNS)
reverse lookup available for the specified host name.
Using Multiple Region Commands
A Region directive can contain more than one command. Multiple commands are evaluated in
order. If a command returns a response such as "access denied" or "password required," the
directive immediately terminates: no other commands are evaluated for the current request.
The ordering of commands within a Region directive can be an important consideration. For
example, suppose that you want to limit the access for a particular region to machines from the
domain that you also want to require a valid user name and password. One way you could do
this is by specifying this Region directive:
Region * {
RequirePassword "Access accountname" -userfile
/server/root/user.db
AllowHost *.compedia.com
}
118 Configuring the iTP Secure WebServer