directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-631) Creation of entry with special (and escaped) character in RDN leads to wrong attribute value
Date Thu, 17 Aug 2006 23:20:15 GMT
    [ http://issues.apache.org/jira/browse/DIRSERVER-631?page=comments#action_12428827 ] 
            
Emmanuel Lecharny commented on DIRSERVER-631:
---------------------------------------------

The code has been modified to handle the vast majority of the cases. However, I still have
an issue remaining : escaped hexPairs.

For instance, the DN :
cn=L\C3\E9charny 

should have this internal value :
cn=L├ęcharny

no?

But in this case, what about :
cn=L\C3charny 

It should generate an exception, because \C3 is not a valid UTF-8 multi-byte char, no?

wdyt ?

PS: the code has not been committed

> Creation of entry with special (and escaped) character in RDN leads to wrong attribute
value
> --------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-631
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-631
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC3
>         Environment: ApacheDS 1.0 RC 3
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Microsoft Windows XP version 5.1 Service Pack 1
>            Reporter: Stefan Zoerner
>         Assigned To: Emmanuel Lecharny
>         Attachments: AddingEntriesWithSpecialCharactersInRDNTest.java
>
>
> If one creates an entry with a special character in its RDN value (e.g. #, <, ...)
which is escaped in the (R)DN, the resulting entries has the escape char (\) in its attribute
value as well. Example:
> Creating this entry:
> dn: cn=Bush\, Kate,dc=example,dc=com
> objectclass: person
> objectclass: top
> sn: Bush
> cn: Bush, Kate
> like this
> $ ldapmodify -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -a -f KateBush.ldif
> adding new entry cn=Bush\, Kate,dc=example,dc=com
> leads to an entry like that
> $ ldapsearch -h localhost -p 10389 -b "dc=example,dc=com" -s sub "(sn=Bush)"
> version: 1
> dn: cn=Bush\, Kate,dc=example,dc=com
> objectclass: person
> objectclass: top
> sn: Bush
> cn: Bush\, Kate
> The expected for cn is "Bush, Kate", as provided by the LDIF above. The same error occurs
with several characters (other than comma). I'll attach a JNDI JUnit test which demonstrates
the issue with test methods using different characters (and the test passes on other directory
servers).
> Note: This problem may be related to DIRSERVER-628.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message