Netscape ENTERPRISE SERVER 6.1, Manual

Page: 28 / 373

Server Instructions in obj.conf
28 Netscape Enterprise Server NSAPI Programmer’s Guide • April 2002 (Draft)
For example:
NameTrans fn="document-root" root="D:/Netscape/Servers/docs"
Directive
indicates when this instruction is executed during the request handling
process. The value is one of
AuthTrans
,
NameTrans
,
PathCheck
,
ObjectType
,
Service
,
Error
, and
AddLog
.
The value of the
fn
argument is the name of the Server Application Function (SAF)
to execute. All directives must supply a value for the
fn
parameter -- if there’s no
function, the instruction won’t do anything.
The remaining parameters are the arguments needed by the function, and they
vary from function to function.
Enterprise Server is shipped with a set of built-in server application functions
(SAFs) that you can use to create and modify directives in
obj.conf
, as discussed
in Chapter 3, “Predefined SAFs and the Request Handling Process.” You can also
define new SAFs, as discussed in Chapter 4, “Creating Custom SAFs.”
The
magnus.conf
file contains
Init
directive SAFs that initialize the server. For
more information, see Chapter 7, “Syntax and Use of magnus.conf.”
Summary of the Directives
Here are the categories of server directives and a description of what each does.
Each category corresponds to a stage in the request handling process. The section
“Flow of Control in obj.conf,” on page 35 explains exactly how the server decides
which directive or directives to execute in at each stage.
•
AuthTrans
Verifies any authorization information (normally sent in the Authorization
header) provided in the HTTP request and translates it into a user and/or a
group. Server access control occurs in two stages. AuthTrans verifies the
authenticity of the user. Later, PathCheck tests the user’s access privileges for
the requested resource.
AuthTrans fn=basic-auth userfn=ntauth auth-type=basic
userdb=none
This example calls the
basic-auth
function, which calls a custom function (in
this case
ntauth
, to verify authorization information sent by the client. The
Authorization header is sent as part of the basic server authorization scheme.