iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)

Using Common Gateway Interface (CGI) Programs
iTP Secure WebServer System Administrator’s Guide523346-002
8-11
Program Access Restrictions
Program Access Restrictions
You can disable access to CGI programs in certain server areas by using the Deny
command in a Region directive. For example, the directive
Region /~*.cgi* {
Deny
}
denies access to all CGI programs located in user directories, that is, any directory
accessed by a URL beginning with a forward slash followed by a tilde (/~).
Passing CGI Environment Variables
You use environment variables to pass descriptive information about the server and
the current request to a CGI program. Some of these variables are set for all requests;
others are set only for particular requests. Passing environment variables is described
in the following three tables:
Table 8-1 on page 8-11 lists and describes the standard environment variables
applicable to generic and Pathway CGI programs.
Table 8-2 on page 8-18 lists and describes additional environment variables
available in the iTP Secure WebServer environment.
Table 8-3 on page 8-21 tells how to use environment variables from specific
programming languages.
The SSL, session identifier, and Secure HTTP environment variables apply only to
secure versions of the iTP Secure WebServer.
Caution. The CGI environment changes on each invocation of CGI_main. To access your
environment variables, use CGI_initialize(), as described under Design Guidelines on
page 8-34.
Table 8-1. Environment Variables (page 1 of 7)
Environment Variable Description
The following environment variables are not request-specific. These variables are set
for all requests.
SERVER_SOFTWARE The name and version of the server software answering
the request and running the gateway.
Format:
name/version
Example:
Tandem iTP Secure WebServer/4.1