Lines Matching refs:URL
32 Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL
35 referral or reference, an LDAP URL describes a service where an LDAP
41 2. URL Definition ..................................................2
43 3. Defaults for Fields of the LDAP URL .............................5
66 document specifies the LDAP URL format for version 3 of LDAP and
87 2. URL Definition
89 An LDAP URL begins with the protocol prefix "ldap" and is defined by
179 The <extensions> construct provides the LDAP URL with an
180 extensibility mechanism, allowing the capabilities of the URL to be
184 extension. These LDAP URL extensions are not necessarily related to
186 unsupported by the client resolving the URL. An extension prefixed
190 If an LDAP URL extension is implemented (that is, if the
194 process the URL. If an extension is not implemented and is not
204 No LDAP URL extensions are defined in this document. Other documents
210 A generated LDAP URL MUST consist only of the restricted set of
236 <filter>, or other element of an LDAP URL.
241 extensions component of the LDAP URL may contain one or more null
244 3. Defaults for Fields of the LDAP URL
246 Some fields of the LDAP URL are optional, as described above. In the
251 to use when it is absent in an LDAP URL that is returned as a
290 above. The first example is an LDAP URL referring to the University
296 The next example is an LDAP URL referring to the University of
305 The next example is an LDAP URL referring to only the postalAddress
315 The next example is an LDAP URL referring to the set of entries found
323 The next example is an LDAP URL referring to all children of the c=GB
331 The next example is an LDAP URL to retrieve the mail attribute for
347 the filters-quoting mechanism and the URL-quoting mechanisms.
355 character must be escaped in a URL, the \s are percent-encoded as %5c
356 (or %5C) in the URL encoding.
359 representation of the DNs-quoting mechanism and URL-quoting
364 The DN encoded in the above URL is:
406 The general URL security considerations discussed in [RFC3986] are
418 the URL and that no security policies are violated.
424 conforming to previous LDAP URL specifications, where all LDAP
429 a way to control URL processing.
433 server or to eavesdroppers in transit and should not be used in URL
438 much preferred. If the URL represents a referral for an update
443 The LDAP URL format allows the specification of an arbitrary LDAP
444 search operation to be performed when evaluating the LDAP URL.
445 Following an LDAP URL may cause unexpected results, for example, the
455 search. The security implications of resolving an LDAP URL are the
523 The LDAP URL format was originally defined at the University of
571 The following technical changes were made to the contents of the "URL
578 the URL, and a note was added to remind the reader of this
586 data used to construct an LDAP URL: "[" and "]" (these two characters
591 the URL. It is believed that existing implementations of RFC 2255
604 elements appear in the URL.
639 "URL Definition" section: removed second copy of <ldapurl> grammar
656 "Defaults for Fields of the LDAP URL" section: added; formed by
657 moving text about defaults out of the "URL Definition" section.
661 "URL Processing" section: removed.
664 example.net hostnames. Added missing '?' to the LDAP URL example
669 demonstrates the interaction between DN escaping and URL percent-
670 encoding. Added some examples to show URL equivalence with respect
679 to the <dn> portion of the URL. Used uppercase in some examples to