[
https://issues.apache.org/jira/browse/SLING-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871082#comment-13871082
]
Alexander Klimetschek commented on SLING-1158:
----------------------------------------------
It should also be possible without having to configure all your selectors
again, since you already configured the valid selectors in your servlets or in
your scripts.
So some (global?) flag for the sling engine could say
"only.configured.selectors" etc. and after evaluation of all possible servlet
candidates - when none matches "exactly" and sling falls back to a lower level
(say an unknown selector "malicious" is used, and there is no servlet
registered for it, and sling would take the non-selector servlet), it would
simply result with a 404.
> 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)
