Installation guide

Support for Multiple Gateway Instances
26 Red Hat Directory Server Gateway Customization Guide • April 2005
Specifying Gateway Configuration to 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.
GET Operations (GCONTEXT)
In a GET operation, gateway CGIs get the gateway context from the QUERY STRING in the
URL.
Use the
GCONTEXT directive in all URLs to gateway CGIs. Embed
<!--GCONTEXT -->
after the CGI name, as shown in the example that follows. 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. An example of embedding
the
GCONTEXT string in a link follows:
<a href=/clients/dsgw/bin/lang?<!-- GCONTEXT
-->&file=auth.html>click</a>
POST Operations (PCONTEXT)
In a POST operation, the CGI posts to the gateway instance specified by a hidden variable
on an HTML form. Each
POST operation to a gateway CGI in an HTML form must use the
PCONTEXT directive so that CGIs can pass the gateway instance to the next page and
maintain the state.
For CGI invocations using a
POST, put
<!-- PCONTEXT -->
at the beginning of a line. For example, you can specify
PCONTEXT in an HTML form as
follows:
<form method=post action=/clients/dsgw/bin/dosearch>
<input type=hidden name=dn value=””>
<!-- PCONTEXT -->
</form>
For more information about content-related directives, see “Context-Related Directives,”
on page 109.
URLs for Gateway Access
To access a gateway, users enter the following URL: