|
From: Alon Bar-L. <alo...@gm...> - 2014-05-20 21:46:40
|
On Wed, May 21, 2014 at 12:37 AM, Neil A. Wilson <nei...@un...> wrote: > On 05/20/2014 04:01 PM, Alon Bar-Lev wrote: >>> >>> Assuming that this is a network packet capture, then Active Directory is >>> generating including that extra byte in the message. The LDAP SDK isn't >>> generating it. >> >> >> I did not claimed the SDK generates that :) >> >> I just think that in the case of C strings, the SDK should remove >> terminating NULL when it converts the content into Java string. > > > I disagree with that. > > Assuming that Microsoft did not actually intend to include the null > terminator in this message, then they should fix their product. If they did > actually intend to include the null terminator for some reason, then it is > not appropriate for the LDAP SDK to silently drop it. > > The LDAP SDK does not attempt to interpret textual messages. It is correct > to make the response available exactly as it was returned by the server, > even if it contains non-printable characters, typographical errors, > grammatical errors, factual errors, profanity, etc. Fair enough. Luckily the 0 is valid utf-8 char, so conversion not fail. I just truncate it. Thanks! |
