[
https://issues.apache.org/jira/browse/SLING-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871282#comment-13871282
]
Alexander Klimetschek commented on SLING-1158:
----------------------------------------------
Ah, you are right. One could set such a flag on individual servlets/resource
types, for the ones where you know the set of selectors is fixed.
But I guess a central whitelist can be easier to maintain in the end.
> 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)
