[OAK-5260] Incorrect handling of subpaths with leading left curly bracket

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.12, 1.5.17, 1.6.0
• Component/s: jcr
• Assignee: Thomas Mueller
• Reporter: Bertrand Delacretaz
• Created: 09/Dec/16 14:40
• Updated: 16/Feb/21 09:52
• Resolved: 22/Dec/16 11:17

Description

As per SLING-6383 it looks like the Oak name mapping causes for example getItem("/libs/{sub") (with a left curly bracket in the path) to return the /libs node if that exists but the supplied path does not.

I'll attach a patch with a test that demonstrates this.

Felix Meschberger mentions in that Sling issue that the parsing of the CR 2 section 3.2.5.1 Expanded Form could be involved, treating the left curly bracket in a special way that's not appropriate here.

Issue Links

• blocks: SLING-6383 Unexpected behavior with left curly bracket in resource resolution
• is related to: OAK-5410 Backport OAK-5260 (Incorrect handling of subpaths with leading left curly bracket)
• is related to: OAK-5367 Strange path parsing