[
https://issues.apache.org/jira/browse/SLING-13000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated SLING-13000:
-----------------------------------
Summary: ResourceResolver: consistent handling of "allowed_alias_locations"
(was: Resource Resolver: consistent handling of "allowed_alias_locations")
> ResourceResolver: consistent handling of "allowed_alias_locations"
> ------------------------------------------------------------------
>
> Key: SLING-13000
> URL: https://issues.apache.org/jira/browse/SLING-13000
> Project: Sling
> Issue Type: Sub-task
> Components: ResourceResolver
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
>
> This once was introduced to reduce the result set for the "optimized"
> (cached) case.
> WIth the recent changes, the cache can by filled in the background. During
> that time, a code path similar to the old code path (without support for
> "allowed_alias_locations") is used, thus whether an alias gets processed
> depends on timing.
> We should either remove the feature or implement it consistently.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
