[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#6261) Misparsing when commas present in LDAP URL DNs

jwm@horde.net wrote:
> Full_Name: John Morrissey
> Version: RE24
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (66.133.190.110)
>
>
> libldap's ldap_url_parselist_int() splits URLs on spaces (" ") and commas
> (",") when parsing them. Commas in LDAP URLs do not need to be
> percent-encoded (in fact, section 4 of RFC 4516 has a number of examples
> with non-encoded commas).

> Perhaps this is a documentation bug. In that case, ldap_open(3) should
> mention this behavior, especially since it conflicts with RFC 4516.

Looks like a doc bug to me. Note that the commandline tools state explicitly:

       -H ldapuri
               Specify URI(s) referring to the ldap server(s); a list  of  URI,
               separated  by  whitespace or commas is expected; only the protoâ??
               col/host/port fields  are  allowed.

The ldap_open(3) manpage should say the same.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/