On Thu, 2018-11-08 at 00:12 +0100, Michael Ströder wrote:
On 11/7/18 11:22 PM, William Brown wrote:
> On Sat, 2018-11-03 at 21:46 +0100, Michael Ströder wrote:
> > I vaguely remember that 389-DS also implements deref search
> > control
> > [1].
> >
> > My question as a client developer:
> > How does 389-DS deal with reference attributes being absent?
>
> I am assuming that you mean a request for dereference where no
> attributeList is requested?
No, I meant the attributes holding the reference are not present in
the
entry.
To be clear that I understand the problem, can you send an example case
of what is occuring? Thanks,
>
> > Off the top of my head, I do not know, but
> > this is something we should check to see if our behaviour is
> > correct
> > according to the provided RFC. Reading the RFC it doesn't seem to
> > specify how an empty attributeList should be handled, but in my
> > view,
> > it should "do nothing" since no attributes were requested.
>
> The I-D does not say much about error conditions.
>
> But I also think if anything's missing the server should simply
> return
> what's present and can be returned but not error out.
>
> > > [1]
https://tools.ietf.org/html/draft-masarati-ldap-deref-00
>
> Ciao, Michael.
>