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

Re: ldapsearch, values with trailing whitespace (ITS#1321)

At 07:32 AM 2001-09-07, Stig@OpenLDAP.org wrote:
>On Fri, Sep 07, 2001 at 08:03:02AM +0000, hharnisch@hbv.de wrote:
>> When I return an Attribute with 2 trailing spaces as a result to
>> a search-request, the ldapsearch-client (from openldap) does not 
>> show the result in an appropriate way.  E.g. instead of
>>   cNAMERecord: www.bauer.com
>> I get
>>   cNAMERecord:: d3d3LmJhdWVyLmNvbSAg
>> The surrounding attributes are all okay.  When I strip off the
>> whitespace in my search-shell-backend everything is fine.
>> Other Ldapclient (e.g. gq, lbe) show the right values with or
>> without trailing spaces.
>You get the value in base64, this may not be a good thing, but OTOH it
>is hard to know that the value includes trailing spaces if the string
>is simply printed.

Or when LDIF is cut and pasted from window to window, trailing
spaces are often dropped.  And some editors automatically
trim trailing white space.  Base64 such values prevents a number
of errors from occurring.  As LDIF is an intermediate format,
the presentation form shouldn't matter greatly.