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

Re: LDAPURLs and Referrals (was: Draft Minutes)




"Kurt D. Zeilenga" wrote:

> At 11:55 PM 12/7/99 -0800, Howard Chu wrote:
> >In RFC2255 the trailing '/' *is* optional, but the difference between these
> >two cases still isn't spelled out.
>
> There is no difference.  Both:
>         ldap://server
>         ldap://server/
>
> specify invalid searches (a subtree search of a NULL DN is invalid)

why subtree search of a NULL DN is invalid ?
Is it mentioned in RFC 2251 ?

>
> but are not invalid URLs.
>
> >It makes sense that there should be a
> >difference in meaning between these two cases, because it's reasonable to
> >want an LDAPURL that can point to the rootDSE of a server.
>
>         ldap://server/??base refers to the rootDSE
>         ldap://server/??one refers to top-level entries that might
>                 by held by the server such as "c=US", "dc=COM"
>         ldap://server/??subtree is invalid search
>
> from this:
>         ldap://server
>         ldap://server/
>
> and represent invalid searches.  However, namedref says
> such URLs, when returned as protocol referrals imply that
> the client should use the base/DN of the operation which
> returned the referral.
>
> Since a server would not ever return a referral "ldap:///??base";
> for any operation, no ambiguity exists.