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-42
Implementing Multiple-Host Support
For example, you could specify the directive
Accept -transport /G/ZTC0 -address 16.11.96.5
in the configuration file of one of two servers, to limit this server to accepting
connections only on IP address 16.11.96.5.
Similarly, you could specify the directive
Accept -transport /G/ZTC0 -address 16.11.96.6
in the configuration file of the other server, to limit this server to accepting connections
only over IP address 16.11.96.6.
You can specify a host name instead of an IP address in an
Accept directive by using
the -address option. The host name specified must correspond to a local IP address,
then the server automatically uses that IP address. For example:
Accept -transport /G/ZTC0 -address www.widgets.com
Again, each of the servers assigned a different IP address is completely independent of
the others. Each has its own configuration file, log files, and content areas.
For further details on the
Accept directive, see Accept on page A-2.
Implementing Virtual Hosts
Another way to configure a server for multiple-host support is to configure a single
server process into virtual hosts, with each virtual host checking for requests on a
different IP address and/or port. Configuring a single server process to support multiple
virtual hosts involves:
•
Establishing virtual IP addresses, as described in Establishing Alias IP Addresses on
page 7-41
•
Setting Up Virtual Hosts (See below)
Setting Up Virtual Hosts
You can cause one iTP Secure WebServer to function as multiple servers by setting up
multiple virtual hosts. Each virtual host can be configured to check for requests on a
different IP address and/or port and can be mapped to host a specified region on the
server.
Create virtual hosts by using the
Accept and/or AcceptSecureTransport directives
to associate specific IP addresses with specific host names and/or ports. Then associate
content regions with these virtual hosts by using Region directives, using the -host
and/or -port arguments.