[ https://issues.apache.org/jira/browse/SLING-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949161#comment-13949161 ]
Carsten Ziegeler commented on SLING-3043: ----------------------------------------- In general, the idea is to get away with vanity paths stored in the resource tree but rely solely on /etc/maps. However, to solve today's problems (until the above is in place), it makes sense to have a whitelist from where vanity paths are read. This can simply be prefixes > Allow regexp filtering of vanity paths > -------------------------------------- > > Key: SLING-3043 > URL: https://issues.apache.org/jira/browse/SLING-3043 > Project: Sling > Issue Type: Bug > Components: ResourceResolver > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > Labels: vanity > Fix For: Resource Resolver 1.1.0 > > > Right now a sling:vanityPath can appear anywhere in the resource tree and it > can point to any other location in the tree. In some cases, it's helpful to > limit the possibilities. > Therefore we should add regexps to exclude certain parts in the tree for > scanning and another set of regexps for filtering the location -- This message was sent by Atlassian JIRA (v6.2#6252)