This document is obsolete. Please
refer to RFC 2254.
Network Working Group T. Howes Request for Comments: 1960 University of Michigan Obsoletes: 1558 June 1996 Category: Standards Track
A String Representation of LDAP Search Filters
Status of this Memo
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
The Lightweight Directory Access Protocol (LDAP)  defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters.
where the LDAPString above is limited to the IA5 character set. The AttributeType is a string representation of the attribute type name and is defined in . The AttributeValue OCTET STRING has the form defined in . The Filter is encoded for transmission over a network using the Basic Encoding Rules defined in , with simplifications described in .
<attr> is a string representing an AttributeType, and has the format defined in . <value> is a string representing an AttributeValue, or part of one, and has the form defined in . If a <value> must contain one of the characters '*' or '(' or ')', these characters should be escaped by preceding them with the backslash '\' character.
Howes Standards Track [Page 2]
RFC 1960 LDAP Search Filters June 1996
Note that although both the <substring> and <present> productions can produce the 'attr=*' construct, this construct is used only to denote a presence filter.