Netscape ENTERPRISE SERVER 6.1, Manual

Page: 31 / 373

The <Object> Tag and the <Client> Tag
Chapter 2 Syntax and Use of obj.conf 31
The <Object> Tag and the <Client> Tag
This section discusses the use of
<Object>
and
<Client>
tags in the file
obj.conf
.
<Object>
tags group together directives that apply to requests for particular
resources, while
<Client>
tags group together directives that apply to requests
received from particular clients.
• The Object Tag
• The Client Tag
The Object Tag
Directives in the
obj.conf
file are grouped into objects that begin with an
<Object>
tag and end with a
</Object>
tag. The default object provides
instructions to the server about how to process requests by default. Each new
object modifies the default object’s behavior.
An
Object
tag may have a
name
attribute or a
ppath
attribute. Either parameter
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
NameTrans
stage of the default object if either of the following
conditions is true:
• The successful
NameTrans
directive specifies a
name
argument
• the physical pathname that results from the
NameTrans
stage matches the
ppath
attribute of another object
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
Service
stage) as soon as one is successfully
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.