Справочник Пользователя для Red Hat Version4.1
Support for Multiple Gateway Instances
6 Netscape Directory Server Gateway Customization Guide
The .conf files defining the configuration of gateway instances are stored in
<NSHOME>/dsgw/context. Within the .conf file are two parameters specifying
the path names for the HTML and template files for the gateway (see
Example 1.1).
<NSHOME>/dsgw/context. Within the .conf file are two parameters specifying
the path names for the HTML and template files for the gateway (see
Example 1.1).
Example 1.1 HTML and configuration directories specified in pb.conf
htmldir../pbhtml
configdir ../pbconfig
Specifying Gateway Configuration to
Gateway CGIs
Gateway CGIs
Information about which .conf file to use is communicated in the QUERY
STRING using a GET, and through a hidden variable on a POST.
STRING using a GET, and through a hidden variable on a POST.
GET Operations (GCONTEXT)
In a GET operation, gateway CGIs get the gateway context from the QUERY
STRING in the URL.
STRING in the URL.
Use the GCONTEXT directive in all URLS to gateway CGIs. Embed <!--
GCONTEXT --> after the CGI name, as shown in Example 1.2. This directive
will be replaced by the current CGI’s gateway context. The GCONTEXT
directive is the only gateway directive that does not have to be at the beginning
of the line.
GCONTEXT --> after the CGI name, as shown in Example 1.2. This directive
will be replaced by the current CGI’s gateway context. The GCONTEXT
directive is the only gateway directive that does not have to be at the beginning
of the line.
Example 1.2 Embedding GCONTEXT in a Link
<a href=/dsgw/bin/lang?<!-- GCONTEXT -->&file=auth.html>click</a>
Gateway 3.x Note
In release 3.x, CGIs passed their arguments using PATH_INFO. In 4.0,
PATH_INFO is replaced by the QUERY_STRING, which works better with the
Japanese version of Windows NT, and is functionally equivalent.
PATH_INFO is replaced by the QUERY_STRING, which works better with the
Japanese version of Windows NT, and is functionally equivalent.