Netscape ENTERPRISE SERVER 6.1, Manual

Page: 33 / 373

The <Object> Tag and the <Client> Tag
Chapter 2 Syntax and Use of obj.conf 33
The URL
http://
server_name
/internalplan1.html
would be translated to
D:/Netscape/Servers/docs/internalplan1.html
. However, suppose that
obj.conf
contains the following additional object:
In this case, the partial path
*internal*
matches the path
D:/Netscape/Servers/docs/internalplan1.html.
So now the server starts
processing the directives in this object before processing the remaining directives
in the default object.
The Client Tag
The
<Client>
tag can be used within an object to limit the execution of a set of
directives to requests received from specific clients. Directives listed between a pair
of
<Client> </Client>
tags are executed only if information in the client request
matches the parameter value specified by the
<Client>
tag.
A
<Client>
tag accepts the parameters
ip
,
dns
, or
host
. Use one and only one of
these parameters to specify the client information to match.
You can use wildcards to specify
<Client>
tag parameter values. For example:
<Object ppath="*internal*">
more directives...
</Object>
Table 2-1 <
Client>
Tag Parameters
Parameter Description
ip
The IP address of the client.
dns
The DNS name of the client.
urlhost
The DNS name of the virtual server requested by the
client. This value is provided in the
Host
header of the
client request. This is how virtual servers were defined
in earlier versions of Enterprise Server. See the Netscape
Enterprise Server Administrator’s Guide for information
on how Netscape recommends implementing virtual
servers in Enterprise Server 6.1.