Search Scope; Extended Operation Oid - Netscape DIRECTORY SERVER 6.1 Configuration Manual

Access Log Content
If the client uses a position-by-value VLV request, the format for the first part, the
request information, would be:
The example below shows VLV-specific entries in bold:
[07/May/2002:11:43:29 -0700] conn=877 op=8530 SRCH
base="(ou=People)" scope=2 filter="(uid=*)"
[07/May/2002:11:43:29 -0700] conn=877 op=8530 SORT uid
[07/May/2002:11:43:29 -0700] conn=877 op=8530 VLV 0:5:0210 10:5397
(0)
[07/May/2002:11:43:29 -0700] conn=877 op=8530 RESULT err=0 tag=101
nentries=1 etime=0
In the above example, the first part,
beforeCount
afterCount
value
and the second part,
targetPosition
contentCount
(resultCode)

Search Scope

The entry
value of 0, 1, or 2.
= base search
0
= one-level search
1
= subtree search
2
For more information about search scopes, see section "Using ldapsearch" in
Appendix B, "Finding Directory Entries" of Netscape Directory Server
Administrator's Guide.

Extended Operation OID

An extended operation OID, in this case either
oid="2.16.840.1.113730.3.5.3"
provides the OID of the extended operation being performed. Table 5-1 provides
the list of LDAPv3 extended operations and their OIDs supported in Directory
Server.
196 Netscape Directory Server Configuration, Command, and File Reference • August 2002
= 0
= 5
= 0210
10:5397 (0)
= 10
= 5397
= (0)
defines the scope of the search performed, and
scope=n
beforeCount:afterCount:value
, is the VLV request information:
0:5:0210
, is the VLV response information:
EXT
or
EXT oid="2.16.840.1.113730.3.5.5"
can have a
n
,