iTP Secure WebServer System Administrators Guide (Version 7.5+)

Table 16 Environment Variables (continued)
DescriptionEnvironment Variable
These environment variables are request specific.
The name and revision of the information protocol this
request came in with.
Format:
SERVER_PROTOCOL
protocol/revision
Example:
HTTP/1.0
The port number to which the request was sent.
Format:
SERVER_PORT
number-between-1-and-65535
Example:
80
Extra path information given by the Web client. CGI
programs can be accessed by their virtual path name
PATH_INFO
followed by extra information. This extra information is
contained in the PATH_INFO variable. If this information
comes through a URL, it is decoded by the server before it
is passed to the CGI program.
Format:
/dir1/dir2/dir3.../file
Example:
/images/logo.gif
The translated version of PATH_INFO, after the server
applies a virtual-to-physical mapping to it.
Format:
PATH_TRANSLATED
/dir1/dir2/dir3.../file
Example:
The partial path /images/logo.gif becomes the full path
name:/root/server/images/logo.gif
The method by which the request was made. For HTTP,
this is GET, HEAD, POST, and so on.
Format:
REQUEST_METHOD
method
A virtual path to the CGI program being executed, used
for self-referencing URLs.
Format:
SCRIPT_NAME
/dir1/dir2/program_name
Example:
/search/name.cgi
The information following the question mark (?) in the URL
referencing this CGI program. This information is not
QUERY_STRING
decoded by the server. This variable is set whenever there
is query information, regardless of command-line decoding
(see “HTML Forms” (page 156)).
The name of the host making the request. If the iTP Secure
WebServer does not know this name, it leaves this variable
REMOTE_HOST
unset. To use this feature, you must enable DNS lookups
by including the ReverseLookup directive, with a value of
yes, in your configuration file.
Format:
machine.domain.category
Example:
www.company.com
Passing CGI Environment Variables 147