D.4.2 Shared Machine, Shared Web Server

In certain ISP environments, customers shared both the physical hardware and the Web server itself. In this environment, a single Web server installation is configured to answer requests for each customer's host name (virtual host). Chili!Soft ASP is compatible with this shared server model.
D.4.2.1 Netscape
The architecture of the Netscape server does not allow for one Netscape process to answer for more than one virtual host (i.e. www.myserver.com and www.yourserver.com). To add an additional virtual host, you must add an additional server using the Netscape Administration tool. You must also add an additional Chili!Soft ASP server for each Netscape server that you add.
Use the add_server script in the Chili!Soft ASP installation directory to add additional Chili!Soft ASP servers. This is the same process described in Shared Machine, Dedicated Web Server section.
D.4.2.2 Apache
The architecture of the Apache server gives you two options for serving two domain names (i.e. www.myserver.com and www.yourserver.com) from the same machine. The first option is to add additional instances of the Apache server (similar to the Netscape model). As with Netscape, if you add additional instances of the Apache server, you will need to add additional Chili!Soft ASP servers. Use the add_server script in the Chili!Soft ASP installation directory to add additional Chili!Soft ASP servers. This approach has the advantage of providing each customer on a box with their own server, such that a restart of one customer's server does not affect the other customer(s). The disadvantage is that it consumes more system resources for a given number of hosts.
The second approach with Apache is to add virtual hosts to the Apache configuration file. This approach allows one instance of the Apache server to serve more than one domain name. Furthermore, only one instance of the Chili!Soft ASP server is required. This approach is valuable because it does the best job of conserving system resources. The downside of this approach is a server restart to fix a problem would affect all of the customers using the server.
By default, Chili!Soft ASP will enable ASP functionality for all virtual hosts defined in the Apache configuration file. You may, however, limit ASP functionality to only certain virtual hosts by adding a [virtual hosts] section the Chili!Soft ASP casp.cnfg file. For example, in the following casp.cnfg file:
[machines]
count=1
machine1=127.0.0.1
portnumber=3456
logfile=/opt/casp/casplog
mtengine=0
disablerestart=0
[default machine]
maxprocesses=5
inherit_user=1
[applications]
use_aliases=no
[virtual hosts]
allow_all=no
timeout=60
www.customer1.com
www.customer2.com
www.customer3.com
The allow_all=no attribute limits ASP functionality to only the virtual hosts specified in the [virtual hosts] section. In this example, the customer1, customer2 and customer3 virtual hosts have ASP functionality enabled. For more information on the settings and sections in the casp.cnfg file, see the Unix Configuration File section in the Chili!Soft ASP Configuration chapter.
Copyright © 2000 Chili!Soft
|