Feature #46
Support base64 values
| Status: | Closed | Start: | 27/04/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | Jonathan Clarke | % Done: | 100% |
|
| Category: | Core | |||
| Target version: | 1.1.0 |
Description
LDAP values in LDIF interchange format are defined like the following :
value-spec = ":" ( FILL 0*1(SAFE-STRING) /
":" FILL (BASE64-STRING) /
"<" FILL url)
Value data that do not fit within a portable subset of ASCII characters are marked with '::' after the attribute name and encoded into ASCII using base64 encoding. See [[http://www.ietf.org/rfc/rfc2849.txt]] for more information.
It should be interesting to allow base64 encoding for unsupported characters. Feature or not ?
Associated revisions
Change names of Base64 methods to explicitly mention base64. References #46.
Base64 encode values if necessary in LDIF output. Fixes #46. Stop using I18N framework for LDIF format, since it does not need translating
History
Updated by Jonathan Clarke over 1 year ago
I think we only use LDIF in the logger, to output changes to the console or a file, don't we?
If so, this would be simple to add in LocalizedJndiModificationsLayout, if we can easily detect when a string contains characters outside the portable subset.
Updated by Jonathan Clarke about 1 year ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset r229.
Updated by Jonathan Clarke about 1 year ago
- Category set to Core
- Assigned to set to Jonathan Clarke
- Target version set to 1.1.0
Updated by Jonathan Clarke about 1 year ago
- Status changed from Feedback to Closed