[Date Prev][Date Next]
Re: (ITS#5540) Normalization assertion in attr.c
On Tue, Jun 24, 2008 at 12:50 PM, Sean Burford <email@example.com> wrote:
> namingContexts was the trickiest, since RFC 4512 defines it without an
> equality matching rule but monitor_back_register_database() compares
> it with backend suffixes. It has to deal with capitalised values
> properly otherwise we end up with duplicate namingContexts entries, so
> normalization is required.
I have uploaded
which adds a test for various things under cn=monitor. If duplicate
namingContexts creep in (as mentioned above) it detects that.
The duplicate naming contexts thing was fixed by comparing a_vals with
be_suffix, I just wrote the test since there was no existing