
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
27/Aug/06 07:55 AM
|
|
try simple malformed filter like 'blah' and see what happends:
line 1:1: expecting LPAREN, found 'blah'
This is printed out to system.err and no exception results. This is not good because it can hang indefinately.
|
|
Description
|
try simple malformed filter like 'blah' and see what happends:
line 1:1: expecting LPAREN, found 'blah'
This is printed out to system.err and no exception results. This is not good because it can hang indefinately. |
Show » |
|
Within my test cases, I have some search operations here:
https://svn.apache.org/repos/asf/directory/trunks/testsuites/src/main/java/org/apache/ldap/testsuite/ldaptests/jndi/ops/search/IllegalSearchFilterTest.java
The class contains a test method testFiltersWithSyntaxErrors which expects an InvalidSearchFilterException in case of a filter like "This is no filter" or "blah". It works as expected for RC1, but it seems to me that it is the JNDI provider for LDAP on the client side causing the exception (no ApacheDS involved).
How was the error achieved in detail? What does "try simple malformed filter" exactly means? command line tool like ldapsearch?