Table of Contents
Advertisement
In this case, the
parameter passed to
pb
that correspond to
auth-type=basic
NSAPI provides a set of functions for working with
example,
pblock_findval()
"Parameter Block Manipulation Routines," on page 124 for a summary of the most
commonly used functions for working with parameter blocks.
sn (session)
The
parameter is a pointer to a
sn
variables related to an entire session (that is, the time between the opening and
closing of the TCP/IP connection between the client and the server). The same
pointer is passed to each SAF called within each request for an entire session. The
following list describes the most important fields in this data structure.
(See Chapter 5, "NSAPI Function Reference" for information about NSAPI routines
for manipulating the
•
sn->client
is a pointer to a
pblock
address, DNS name, or certificate. If the client does not have a DNS name or if
it cannot be found, it will be set to
•
sn->csd
is a platform-independent client socket descriptor. You will pass this to the
routines for reading from and writing to the client.
rq (request)
The
parameter is a pointer to a
rq
variables related to the current request, such as the request headers, URI, and local
file system path. The same
request-response process for an HTTP request.
The following list describes the most important fields in this data structure (See
Chapter 5, "NSAPI Function Reference," for information about NSAPI routines for
manipulating the
Request
basic-ncsa
and
returns the value for a given name in a
Session
data structure):
Session
containing information about the client such as its IP
-none
request
pointer is passed to each SAF called in the
request
data structure).
contains name/value pairs
dbm=/netscape/server4/userdb/rs
data structures. For
pblock
data structure. This parameter contains
.
data structure. This parameter contains
Chapter 4
Creating Custom SAFs
SAF Parameters
.
. See
pblock
sn
113
Advertisement
Table of Contents
