Table of Contents
Advertisement
Support for Multiple Gateway Instances
Specifying Gateway Configuration to Gateway CGIs
Information about which
a
GET
GET Operations (GCONTEXT)
In a
GET
URL.
Use the
<!--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
directive that does not have to be at the beginning of the line. An example of embedding
the
GCONTEXT
<a href=/clients/dsgw/bin/lang?<!-- GCONTEXT
-->&file=auth.html>click</a>
POST Operations (PCONTEXT)
In a
POST
on an HTML form. Each
PCONTEXT
maintain the state.
For CGI invocations using a
<!-- PCONTEXT -->
at the beginning of a line. For example, you can specify
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:
26
Red Hat Directory Server Gateway Customization Guide • April 2005
.conf
and through a hidden variable on a
operation, gateway CGIs get the gateway context from the
directive in all URLs to gateway CGIs. Embed
GCONTEXT
string in a link follows:
operation, the CGI posts to the gateway instance specified by a hidden variable
POST
directive so that CGIs can pass the gateway instance to the next page and
POST
file to use is communicated in the
.
POST
GCONTEXT
operation to a gateway CGI in an HTML form must use the
, put
QUERY STRING
QUERY STRING
directive is the only gateway
in an HTML form as
PCONTEXT
using
in the
Advertisement
Table of Contents
