You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/04/14 13:29:00 UTC

[jira] [Resolved] (SLING-3692) Provide access to list of vanity paths/aliases in SLING-3505

     [ https://issues.apache.org/jira/browse/SLING-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-3692.
-------------------------------------
    Resolution: Won't Fix

> 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
>            Priority: Major
>
> 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
(v8.20.10#820010)