You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Norval Hope (JIRA)" <ji...@apache.org> on 2009/04/20 04:19:47 UTC

[jira] Closed: (DIRSERVER-1247) removing unrequired escaping in DNs / filters

     [ https://issues.apache.org/jira/browse/DIRSERVER-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norval Hope closed DIRSERVER-1247.
----------------------------------


Thanks Stefan.

The stars didn't align for me porting over to ApacheDS 1.5.x during my last release, but I'm hoping to look at porting over to 1.5.5 in the next month or two. Until then I won't be able to personally verify the final patch, but I'm happy to close the issue for now as the added/modified unit tests verify the behaviour I saw as valid.

> removing unrequired escaping in DNs / filters
> ---------------------------------------------
>
>                 Key: DIRSERVER-1247
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1247
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: ldap
>    Affects Versions: 1.5.4
>            Reporter: Norval Hope
>             Fix For: 1.5.5
>
>         Attachments: DIRSERVER-1247-escaping-2.patch, escaping.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> The current Dn and filter handling is overly restrictive in that all non-ascii characters are quoted using the \NN syntax. This is probably due to rfc 2253 being unclear about the fact that multibyte UTF-8 encoded values can be used, but this iss further clarified in rfc 4514 which superceeds 2253. The application of unrequired quoting makes debugging / reading logs much harder then it should be, as it requires manual calculations rather then just setting the file encoding on your log file / IDE windows to being UTF-8.
> I have attached a patch file with the required updates to code and unit tests under /shared/ldap (some problems i had noted with earlier AD version due to unspecified encoding when converting bytes to / from Strings had already been tidied up in AD 1.5.4). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.