Table of Contents
Advertisement
The <Object> Tag and the <Client> Tag
This section discusses the use of
<Object>
resources, while
received from particular clients.
•
The Object Tag
•
The Client Tag
The Object Tag
Directives in the
<Object>
instructions to the server about how to process requests by default. Each new
object modifies the default object's behavior.
An
Object
may be a wildcard pattern. For example:
<Object name="cgi">
or
<Object ppath="/usr/netscape/servers/docs/private/*">
The server always starts handling a request by processing the directives in the
default object. However, the server switches to processing directives in another
object after the
conditions is true:
•
The successful
•
the physical pathname that results from the
ppath
When the server has been alerted to use an object other than the default object, it
processes the directives in the other object before processing the directives in the
default object. For some steps in the process, the server stops processing directives
in that a particular stage (such as the
executed, whereas for other stages the server processes all directives in that stage,
including the ones in the default object as well as those in the additional object. For
more details, see ""Flow of Control in obj.conf," on page 35.
tags group together directives that apply to requests for particular
tags group together directives that apply to requests
<Client>
file are grouped into objects that begin with an
obj.conf
tag and end with a
</Object>
tag may have a
name
stage of the default object if either of the following
NameTrans
directive specifies a
NameTrans
attribute of another object
and
<Object>
<Client>
tag. The default object provides
attribute or a
attribute. Either parameter
ppath
name
NameTrans
stage) as soon as one is successfully
Service
Chapter 2
The <Object> Tag and the <Client> Tag
tags in the file
obj.conf
argument
stage matches the
Syntax and Use of obj.conf
.
31
Advertisement
Table of Contents
