Previous PageNext Page

D.3.1 ASP User Configuration File

In the [applications] section of the Chili!Soft ASP casp.cnfg file, you may specify the name of a file that contains definitions of ASP applications. Sample casp.cnfg [applications] and [virtual hosts] sections appear below:
 

[applications]

use_aliases=no #if yes, Apache aliases are treated as apps.

config_name=.aspconf #name of file containing ASP apps.

/caspsamp="/opt/casp/caspsamp" #these apply only to

/app1="/any/directory/you/want" #the "real host"

[virtual hosts]

allow_all=no #if Yes, no need to list hostnames below.

timeout=60 #time in minutes for timing out a vhost

www.customer1.com #could also be IP address

www.customer2.com

www.customer3.com

Any applications defined in the ASP User Configuration file will be dynamically recognized by Chili!Soft ASP, without requiring Chili!Soft ASP to be restarted. If config_name=.aspconf, for example, Chili!Soft ASP will look for this filename in the document root of the Web server (and each virtual host). Entries in the ASP User Configuration file should use the following format:
 

/[appname] = "/path/to/app/home/directory"

If the ASP User Configuration file appears in the document root of a virtual host, then the ASP applications will only be applied to that virtual host, and not to others.
 
There are two limitations on applications defined in the ASP User Configuration file. First, the files in the application must be located within the document root of the Web server (or virtual host). Second, the directory containing the Global.asa file may not be below the top-level directory of the Web server's (or virtual host's) document root. For more information on ASP applications and the Global.asa file, see Chapter 5: ASP Reference.
 

Copyright © 2000 Chili!Soft

Previous PageTop Of PageNext Page