Skip to content
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

Open
ohalluin opened this issue Apr 25, 2016 · 3 comments
Open

error in request with sluggeable path #313

ohalluin opened this issue Apr 25, 2016 · 3 comments

Comments

@ohalluin
Copy link

HTTP 400: Query:
SELECT node.[jcr:uuid] AS uuid FROM [nt:unstructured] AS node WHERE ISCHILDNODE(node, [/cmf/qvdf_fr/contents/formats/test-(*)2e])

in vendor/jackalope/jackalope-jackrabbit/src/Jackalope/Transport/Jackrabbit/Request.php at line 584

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?

@ohalluin ohalluin changed the title error a request error in request whit sluggeable path Apr 25, 2016
@ohalluin ohalluin changed the title error in request whit sluggeable path error in request with sluggeable path Apr 25, 2016
@dbu
Copy link
Member

dbu commented Apr 30, 2016

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. -2e, .3e or %0E have a problem. it does not happen if the character before 2e is something else, and it does not happen with other letters than "e". it happens with all numbers however.

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)

@dbu
Copy link
Member

dbu commented Apr 30, 2016

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)

@dbu
Copy link
Member

dbu commented Jun 9, 2016

created https://issues.apache.org/jira/browse/JCR-3985 on jackrabbit. lets keep this open so we can update if they act on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants