Closed pavelhoral closed 7 years ago
Btw. my suspicion is that the parser is trying to handle the attribute as URL:
bar:< file:///tmp/baz.jpg
However the additional space should make all the difference.
Ok... the error is on my side. The RFC states that the <
(0x3C) is excluded and not included. So there is nothing wrong with this parser.
I was getting confused because I had these values inside LDIF generated from a different tool. It is a nice feature for XML based values though to have them in plain text instead of unreadable Base 64...
The following record will fail to parse:
This is a valid LDIF because according to RFC it is part of SAFE-INIT-CHARS: