[
https://issues.apache.org/jira/browse/DIRSERVER-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1395.
----------------------------------------
Resolution: Invalid
I confirm that '=' is not to be escaped in a RDN, at meast, it's not mandatory.
RFC 4514, appendix B states so :
- Updated Section 2.4. Indicated that equals sign ('=' U+003D) character
may
be escaped as '\='.
- Updated the Section 3 ABNF. Changes include:
+ did not require escaping of equals sign ('=' U+003D)
characters,
> '=' is being escaped properly in RDN values
> -------------------------------------------
>
> Key: DIRSERVER-1395
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1395
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 1.5.4, 1.0
> Environment: Windows XP
> Reporter: Norval Hope
> Attachments: rdn_value_with_equal.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> A colleague of mine discovered that due to a mistake in a boolean array
> (AttributeTypeAndValue.DN_ESCAPED_CHARS) the '=' character is not escaped
> during RDN normalization when it appears in a RDN value. This may be due to
> http://www.faqs.org/rfcs/rfc2253.html seemingly leaving it in "2.4.
> Converting an AttributeValue from ASN.1 to a String" but then including it in
> the "special = " BNF clause.
> The attached patch fixes the problem, adds a new testcase covering it and
> fixes a few other testcases which tested for the old (broken) behaviour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
