Hi, On Thursday 29 May 2003 20:34, Clifton, Doug wrote: > I have experienced the same results when using straight .ldif files to > load some of the directory servers, but I've not made a definitive study to > see why. The values reload and match properly from what I've experienced, > so we never bothered about it further. It seemed that the single leading > space in a value was enough to convince the directory server that the value > was binary 'blobish' and to handle it as such for all compares,exports, and > imports. We've made attempts to clean up some perl code (not net::ldap) > that had similar problems, so I don't think this is related to net::ldap. > Has anyone seen any RFC info on leading spaces?... It would be good to know > without digging through them if there is something about it ... > Doug.
The interesting RFC is the one about LDIF: RFC 2849 What you call binary is just some form of input/output encoding to let the server know unambigously whether a leading space belongs to the attribute or whether it is part of the LDIF file syntax. Peter -- Peter Marschall eMail: [EMAIL PROTECTED]
