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

Re: LDAPprep: mapping of " " values

At 08:30 AM 11/18/2004, Hallvard B Furuseth wrote:
>Hallvard B Furuseth writes:
>>> My view is that (l=foo * bar) since "foo X bar" without
>>> consuming any portion of X, it should match "foo  bar"
>>> (which passes your disjoint concern), and since "foo bar"
>>> is equivalent, that too.
>>
>> The _prepared_ substrings are matched with the _prepared_ attribute
>> value.  E.g. in [Syntaxes] 4.2.6 (caseExactSubstringsMatch).
>
>I've lost track of this... Is each substring prepared separately?

At presently specified, yes.

>Then the spaces in the filter disappear, and it matches "foobar".

Right. And that's a problem.  (l=foo *) and (l=* bar) should not
match "foobar", that's plain wrong IMO.

>Otherwise, if the substringAsssertion is prepared before splitting it
>at the '*'s, then hex-escaped characters are going to be troublesome.

Whether or not the assertion was presented via the string
representation or via some other means, is irrelevant to
the protocol and the matching.

Kurt