[Date Prev][Date Next]
Bug In RfcFilter.java prohibits escaped filters (ITS#2500)
Full_Name: Will Wood
Submission from: (NULL) (126.96.36.199)
There's a bug in RfcFilter.java in JLDAP
that prohibits an escaped search filter from being properly addressed. This is
in the latest CVS drop.
in unescapeString, a variable temp is being declared and initialized for each
escaped hex digit, therefore the high order bits are always being chucked.
Solution move the
declaration outside of the for loop and re-initialize when the escape character
is hit. I've also reported this bug to Novell as well, however I'm curious as
no JUnit test caught the failure of using escaped values?
> char temp = 0;
< char temp = 0; // get the value of the excaped sequence
> temp = 0; // wipe out any old bits.