### Common settings

#### Timeout

Time permitted for page/file execution.

#### Treat as script engine

The file extension is treated as one processed by a script engine. This concerns the directory setting Run Scripts.

#### Check that file exists

If checked ALP will check if the file exists before invoking the configured content generator module and/or CGI processor.

### ASP processor (ScriptGen)

#### Default script language

The default script language assumed if no Language ASP directive exists in the page.

#### IIS compatibility level

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.

#### Enable parent paths

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).

### RAW scripts (ScriptGen)

#### Script language

The script language in which the raw scripts with this file extension are written.

#### Library files

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).

### gateCGI (CGI handling)

#### CGI Processor

The CGI scripts or executables may vary in the way they must be invoked. In general there are two types of CGI applications:
Executed by the system: These are executables and batch files for example. They do not need any additional settings. It is enough to specify that the extension should be handled by the system and ALP will permit this and expect the usual CGI output.
CGI Processors: These are various processors (almost always EXE files) such as script processors (Perl, PHP etc.) which are executed with the current file as parameter. The way they expect the input file to be given to them may vary. Also they may be able to accept additional parameters or command line options. Most often such applications are designed to require two parameters like this: exefile.exe "%s" %q , but there are also many exceptions or additional parameters supported (consult your CGI processor documentation). To cope with this ALP supports extended command line syntax. You can use the following variables in the command line:

- %m - is replaced with the full physical path containing the GateCGI module (dll)
- %r - is replaced with the full physical path of the ALP site root
- %p - is replaced with the full physical path from the URL - i.e. physical path corresponding to the current URL
- %s - is replaced with the full physical path of the script file - i.e. physical equivalent of the URL
- %q - is replaced with the query string

Note that quotes should be placed around the variables resolved to full paths for they may contain spaces.
The path to the processor executable can be specified in 3 possible ways - full physical path (or just the exe file if it is in the system PATH variable), relative to the ALP site root (such as \bin\mycgi.exe) and relative to the ALP engine DLL (this should be used only with autorun applications where own copy of the ALP engine is on the CD with all the additional files/processors the application needs).

#### Show error output

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.

#### Additional environment variables

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.

### Simple HTML template

#### Global variables

One variable on each line for example:
A=Some text
B=Other text
The variables can be replaced in the templates.