iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)
Configuring the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—523346-002
7-35
Disabling Logging
For more information about the DirectoryIndex command, see Region on 
page A-39.
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 use the NoLog command in a Region 
directive as follows:
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 the following 
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 you wish to limit the access for a particular region 
to machines from the domain compedia.com; you also wish to require a valid user 










