[
https://issues.apache.org/jira/browse/JCR-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329190#comment-15329190
]
David Buchmann commented on JCR-3985:
-------------------------------------
ah, big decimal. i was wondering if its hexadecimal numbers or url encoding.
that explains why those specific situations lead to problems. but i don't see
why we would want to parse a node name for big decimal. if we accidentally have
a valid big decimal, we would then search for a number instead of a string? the
thing is, even "node-1e" fails... ISCHILDNODE should not accept a number but a
string, or am i missing something?
> jackrabbit remoting fails on number followed by "e"
> ---------------------------------------------------
>
> Key: JCR-3985
> URL: https://issues.apache.org/jira/browse/JCR-3985
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi
> Affects Versions: 2.12.1
> Reporter: David Buchmann
>
> with our PHP client using the jackrabbit remoting, we found a very strange
> bug. when we try to query for a node with ISCHILDNODE and a name that has -,
> . or %, followed by a number and then followed by e or E, we get an error 400
> response. I tried the same with a simple java client to see if we do
> something wrong on our side, but the result is the same.
> so what does not work are names like `-2e`, `.3e` or `%0E`
> the problem does not happen if the character before <NUMBER>e is something
> else, and it does not happen with other letters than "e". it happens with all
> numbers however.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
