Time permitted for page/file execution.
The file extension is treated as one processed by a script engine. This concerns the directory setting Run Scripts.
If checked ALP will check if the file exists before invoking the configured content generator module and/or CGI processor.
The default script language assumed if no Language ASP directive exists in the page.
This option allows you specify the ALP behavior for this application. It can be set
from 0 to 3. Where:
0 - is ALP 1.0 compatible
1,2 - Add more IIS compatibility (behavior of the Session, Application objects etc.)
3 - Corrects some incompatibilities with IIS and is recommended for ported
applications.
If your application faces some difficulties try changing this option and see if it will work correctly.
If it is ported from IIS the highest value is recommended, if it is an
application designed for older
ALP versions try 1 or 0. See detailed information about the features
affected in the ALP documentation.
Affects the include directives and Server.MapPath. If checked no paths containing .. are allowed (this prevents the application from direct mapping/include of files outside the ALP site).
The script language in which the raw scripts with this file extension are written.
For raw scripts you can specify files that will be included each time a raw
script file from this application is processed. The file name can be specified
as:
1: \file or \dir1\....\dirN\file - which addresses the files relatively to the
root of the ALP site.
2: file or dir1\....\dirN\file - which addresses the files relatively to the
location of the currently processed file (use with care).
For CGI developers. When testing the CGI you may have problems following the CGI output as the CGI standard requires at least Content-Type header. If the header is not reported an error occurs and you may not be able to see what is happening if the problem in your CGI prevents it from reporting this header. By checking this ALP is forced to show the output as clear text in case of CGI error.
One variable on each line varname=value. These variables are available in the
environment when the specified CGI executable is started. The CGI also has access to
the ALP defined standard CGI variables.
In addition you can use %varname% syntax in the variable values. if the varname
is a name of one of the ALP defined standard CGI variables or is a name of a variable
defined on a line above it will be resolved in-place. This allows you specify
values dynamically resolved to values dependent on the file location or system specifics
for example.
One variable on each line for example:
A=Some text
B=Other text
The variables can be replaced in the templates.