[
https://issues.apache.org/jira/browse/SLING-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043252#comment-14043252
]
Dominique Pfister commented on SLING-3692:
------------------------------------------
[~justinedelson], I can't say for sure: it is necessary, if a request to Sling
would be handled (not returning a 404) because of some non-vanity entry in
/etc/map, but blocked with our plugin because the requested URL is e.g. not
underneath /content.
bq. Do both of those make sense in this feed? Is that the right format?
No, false positives are ok, so sling:vanityPath alone is enough.
> 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)
