Re: (ITS#3467) URL parsing routines non symmetric; generated URL strings unusable

[Kurt@OpenLDAP.org]

Ando,


  According to RFC 2396's reserved chars,

    <http://www.openldap.org/its/index.cgi/ldap://localhost:389/dc=example>ldap://localhost:389/dc=example,dc=org??sub?(objectClass=*)

should be rewritten as

    <http://www.openldap.org/its/index.cgi/ldap://localhost:389/dc>ldap://localhost:389/dc%3Dexample%2Cdc%3Dorg??sub?(objectClass%3D*)


While it may be written in this way (you can escaping anything),
it is not required as the "," is not special to the LDAP URI form.
See RFC 2255 and RFC 3986.

Note:
    If data for a URI component would conflict with a reserved
   character's purpose as a delimiter, ...

but "," here does not conflict with the reserved character's
purpose as a delimiter as "," and "=" as "," and "=" is not used
as a denominator within these components of the URI.

and:
    URI producing applications should percent-encode data
   octets that    correspond to characters in the reserved set
   unless these characters are specifically allowed by the URI
   scheme to represent data in that component.

"," and "=" are allowed in these components of the URI
by the LDAP URI specification.
Kurt