Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <3203938.1174262829505.JavaMail.jira@brutus>
Date: Sun, 18 Mar 2007 17:07:09 -0700 (PDT)
From: "Norval Hope (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (DIRSERVER-873) Apparent problem in decoding LDAP
 requests
In-Reply-To: <21529998.1174024869399.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DIRSERVER-873?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norval Hope updated DIRSERVER-873:
----------------------------------

    Attachment: Copy of apacheds-rolling.log

Not sure if this Twix log is of any interest after your earlier investigati=
on, but attaching it just in case.

> Apparent problem in decoding LDAP requests
> ------------------------------------------
>
>                 Key: DIRSERVER-873
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-873
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: asn1, ldap
>    Affects Versions: 1.5.0
>         Environment: WindowsXP, JDK 1.5.06
>            Reporter: Norval Hope
>         Attachments: Copy of apacheds-rolling.log, Copy of apacheds-rolli=
ng.log
>
>
> I'm sending a request with a non-seven bit ascii char in a DN from JXplor=
er and it seems to be decoded incorrectly when it arrives at ApacheDS (ASN =
level byte logging is attached). I see the same problem when sending the re=
quest from JMeter too.
> The DN I used was "uid=3Dtt=C3=A9,ou=3Dsystem" (same as uid=3D value in a=
ttributes) but decoded as 'uid=3Dtt\C3\A9,ou=3Dsystem' where I was expectin=
g 'uid=3Dtt\E9,ou=3Dsystem'. The full data I sent was:
> DN: uid=3Dtt=C3=A9,ou=3Dsystem
> cn: tt=C3=A9
> objectClass: inetOrgPerson
> sn: ttsn
> I tried sending the DN as 'uid=3Dtt\E9,ou=3Dsystem' but then JXplorer tri=
ed to quote the '\' itself so it seems that it wants to be responsible for =
the conversion to an rfc2253 compliant DN itself.
> I know all this encoding/codepage/locale/lang stuff is always a big PITA =
and that this may be related to to the default encoding on WinXP or some su=
ch thing, but even then I'm struggling to see how one Latin char '=C3=A9' b=
ecomes two hex chars \C3 and \A9 in UTF8. At any rate I have attached the A=
SN byte logs so that someone more knowledgeable can review and state defini=
tively that the bytes received by AD are already "bad". Note that I ran thi=
s test against the latest 1.5 trunks (after first noticing the issue in my =
own out-of-date a heavily modified version of 1.5)

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