New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error in request with sluggeable path #313
Comments
i started investigating this, and this is absolutely bizarr. i can reproduce the bug, and it only ever happens with a number followed by e or E. i tried the same with a little java test program to see if its a bug on the PHP side but it has exactly the same problem when using the jackrabbit remoting client. it smells a lot like you found a bug in jackrabbit :-( can you please try to take this up with the jackrabbit people? i would expect this to be a problem of the remoting layer of jackrabbit, not of the core search engine (though you never know, but in general the core part is heavily used so this would have been fixed already. the remoting layer is sometimes a bit more flaky) |
oh, please first try with the latest jackrabbit 2.x release if you are using an older version, to be sure its not already fixed. and i am glad if you can update me if you hear anything from the jackrabbit people. i wrote a test that demonstrates the problem with jackalope: phpcr/phpcr-api-tests#180 (this will not help the jackrabbit people though) |
created https://issues.apache.org/jira/browse/JCR-3985 on jackrabbit. lets keep this open so we can update if they act on this. |
During a query on a path containing a '-' followed by a number and a letter (eg test-2e), a 400 response appears.
The problem does not occur with 'test-2-e'. This comes about the parser the URL when generating the request?
The text was updated successfully, but these errors were encountered: