Paul Engle wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dieter beat me to the punch on citing RFC 4511 as the authoritative source for
information. However, it doesn't really give guidelines on what result code to
return for this (or any) situation.
Appendix A of the same RFC also gives short descriptions of the result codes, breaking them down into
"Non-Error Result Codes" and "Result Codes". Code 32 falls into the latter. Since that
group is not "Non-Error", I would tend to interpret it to mean that those codes *are* errors.
Not finding what you were searching for is not, in my opinion, a protocol
error. To return an error code for a successful search operation doesn't seem
right to me. Every LDAP directory I've worked with returns a Success (0) for an
empty search result.
http://www.watersprings.org/pub/id/draft-just-ldapv3-rescodes-02.txt
5.2.2.2.1noSuchObject(32)
Applicable operations: all except for Bind.
This error should only be returned if the target object cannot be
found. For example, in a search operation if the search base can not
be located in the DSA the server should return noSuchObject. If,
however, the search base is found but does not match the search
filter, success, with no resultant objects, should be returned
instead of noSuchObject.
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
