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-26
Controlling Access to the Server
For the server in the above example, you would include the following element in the
Accept or AcceptSecureTransport directive:
-name www.compedia.com
After changing the configuration file, you must restart the server as described in
Configuring the iTP Secure WebServer on page 7-1.
4. Test the new configuration by using the new alias in a URL to access the server. For
the server in our example, you would use your web client to access:
http://www.compedia.com/index.html
Controlling Access to the Server
This section describes how to control and monitor access to your server using the
following tasks:
•
Using Region Directives (See below)
•
Granting Access by Host Name/IP Address (See page 7-28)
•
Denying Access by Host Name/IP Address (See page 7-29)
•
Requiring Client Authentication (See page 7-29)
•
Administering Passwords (See page 7-30)
•
Redirecting Access (See page 7-32)
•
Enabling Automatic Directory Indexing (See page 7-33)
•
Disabling Logging (See page 7-34)
•
Using Multiple Region Commands (See page 7-34)
•
Using Pattern Variables (Lists) (See page 7-36)
•
Using Conditional Commands (See page 7-37)
•
Using Tcl Variables (See page 7-37)
•
Allowing Byte Ranges (See page 7-40)
•
Implementing Multiple-Host Support (See page 7-40)
Using Region Directives
You control client access to your server by entering commands in a Region directive in
the server configuration file (httpd.config). The Region directive applies these
commands to any requests or classes of requests attempting to access a specified portion
of your server file tree. Such a specified portion of the server file tree is referred to as a
region.