RFC2255 LDAP URLs, with the following changes:

1) Additionally supports ldaps and ldapi (TLS and Unix Domain variants).

2) Supports familiar (http, ftp-like) [user[:pass]@] syntax before the hostport part of the URL. These are translated into critical bindname and x-bindpw extensions. That is:

ldap://foo:bar@localhost

is treated as:

ldap://localhost/????!bindname=foo,!x-bindpw=bar

We do this for backwards compatability with some applications which used the old AppUtils LDAP module, and because the standard second syntax is quite unpleasant, especially when the bindname DN contains commas that would have to be quoted as %2C in the extensions.

Attributes provided:

host hostname of server (or empty string) port port number (integer, default 389) basedn the dn provided (or empty string) attrs tuple of attributes to retrieve, None if unspecified scope SCOPE_BASE (default), SCOPE_ONELEVEL, or SCOPE_SUBTREE filter search filter (or empty string) extensions dictionary mapping extension names to tuples of (critical, value) where critical is 0 or 1, and value is a string. critical a list of extension names that are critical, so code may easily check for unsupported extenstions and throw an error.

parse (
        self,
        scheme,
        body,
        )