Table of Contents
Advertisement
Required Behavior of SAFs for Each Directive
•
vs_get_doc_root
•
vs_get_httpd_objset
configuration for a given virtual server.
•
vs_get_id
•
vs_get_mime_type
Content-type:
•
vs_lookup_config_var
virtual server.
•
vs_register_cb
notifications of virtual server initialization and destruction events.
•
vs_set_data
slot.
•
vs_translate_uri
specific virtual server.
Required Behavior of SAFs for Each Directive
When writing a new SAF, you should define it to do certain things, depending on
which stage of the request handling process will invoke it. For example, SAFs to be
invoked during the
to be invoked during the
The
rq
throughout the request-response process. On input to a SAF,
values were inserted or modified by previously executed SAFs. On output,
contains any modifications or additional information inserted by the SAF. Some
SAFs depend on the existence of specific information provided at an earlier step in
the process. For example, a PathCheck SAF retrieves values in
were previously inserted by an AuthTrans SAF.
This section outlines the expected behavior of SAFs used at each stage in the
request handling process.
•
Init SAFs
•
AuthTrans SAFs
•
NameTrans SAFs
•
PathCheck SAFs
128
Netscape Enterprise Server NSAPI Programmer's Guide • November 2001
finds the document root for a virtual server.
obtains a pointer to the virtual server class
finds the ID of a virtual server.
determines the MIME type that would be returned in the
header for the given URI.
allows a plugin to register functions that will receive
sets the value of a pointer to data for a given virtual server and
translates a URI as though it were part of a request for a
stage must conform to different requirements than SAFs
Init
Service
parameter is the primary mechanism for passing along information
finds the value of a configuration variable for a given
stage.
contains whatever
rq
rq
which
rq->vars
Advertisement
Table of Contents
