[
https://issues.apache.org/jira/browse/SLING-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-1158:
-------------------------------------
Component/s: (was: Scripting)
ResourceResolver
Yes your observation is indeed right. Is this a problem we have to tackle ? And
if so: in what whay ?
After all, these are all valid URLs and according to how we resolve URLs by
continuously cut at dots, this can be seen as expected behaviour.
> page.....html resolves to same resource as page.html
> ----------------------------------------------------
>
> Key: SLING-1158
> URL: https://issues.apache.org/jira/browse/SLING-1158
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Reporter: Mark Baker
> Priority: Trivial
>
> If /page.html resolves, then /page..html or /page............html also
> resolves to the same resource. I expect this is just a consequence of having
> an empty string as a selector, but probably unintended behaviour.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
