[ https://issues.apache.org/jira/browse/SLING-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042363#comment-14042363 ]
Justin Edelson commented on SLING-3692: --------------------------------------- [~dpfister] Vanity Paths (with or with SLING-3505) aren't differentiated from other mapping entries (i.e. /etc/map). Is this necessary? Also, for every sling:vanityPath, we actually create two map entries: one for the vanity path itself and one with a trailing regex, i.e. a sling:vanityPath of /foo, the created mappings are /foo$ and /foo(\..*). Do both of those make sense in this feed? Is that the right format? > Provide access to list of vanity paths/aliases in SLING-3505 > ------------------------------------------------------------ > > Key: SLING-3692 > URL: https://issues.apache.org/jira/browse/SLING-3692 > Project: Sling > Issue Type: Improvement > Components: ResourceResolver > Affects Versions: Resource Resolver 1.1.0 > Reporter: Dominique Pfister > > In our infrastructure, we're using a web server in front of our application > hosting Sling, and this web server blocks a lot of requests based on their > URL, except those that actually map to a vanity path. In order to keep this > information up to date, a plugin in the web server periodically requests the > list of vanity paths from a servlet registered in Sling. > It would be great if this servlet could have access to the internal list > built in SLING-3505, so it could benefit from the performance gain. -- This message was sent by Atlassian JIRA (v6.2#6252)