[Date Prev][Date Next]
Re: Fw: Reserved characters for a LDAP URI
I'd start with the proper string representation of the URL (from RFC2253),
which states that the "," in the ou value should be escaped as "\2C"
ou=PKI IWG,o=Chunghwa Telecom Co.\2C Ltd.,c=TW
>From there, convert the string form of the DN to a URL, replacing the space
(%20) and \ (%5C) characters:
<firstname.lastname@example.org To: Wen-Cheng Wang <email@example.com>
m> cc: ietf-ldapbis@OpenLDAP.org, firstname.lastname@example.org
Sent by: Subject: Re: Fw: Reserved characters for a LDAP URI
12/23/2002 04:48 AM
Wen-Cheng Wang wrote:
> Taiwan side believes that the DN component in a LDAP URI should
> However, Japan side insists that it should be:
There is one more possibility. ;-)
I think in case of LDAP URLs all these variants are equivalent.
Note that any URL-illegal characters (e.g., spaces), URL special
characters (as defined in section 2.2 of RFC 1738) and the reserved
character '?' (ASCII 63) occurring inside a dn, filter, or other
element of an LDAP URL MUST be escaped using the % method described
in RFC 1738 . If a comma character ',' occurs inside an extension
value, the character MUST also be escaped using the % method.
As I understand this the ',' MUST be escaped in extensions but MAY be
escaped in dn, filter, etc. as well.