[
https://issues.apache.org/jira/browse/SLING-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5672:
-----------------------------------
Description:
Currently if any wildcards are used in the regular expressions for the Root
Mapping Entries
(http://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#root-level-mappings)
the entry is only considered for {{ResourceResolver.resolve(...)}}, i.e.
inward mapping but no longer for {{ResourceResolver.map(...)}}, i.e. outward
mapping.
While this makes sense for the {{URL path}} part it would be good to allow that
for {{scheme}}, {{host}} or {{port}}. So in case there is a wildcard regular
expression being used on level 1 or 2 below the mapping entry root, this entry
should still be considered for both inward and outward mapping.
was:
Currently if any wildcards are used in the regular expressions for the Root
Mapping Entries
(http://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#root-level-mappings)
the entry is only considered for {{ResourceResolver.resolve(...)}}, i.e.
inward mapping but no longer for {{ResourceResolver.map(...)}}, i.e. outward
mapping.
While this makes sense for the URL path it would be good to allow that for
scheme, host or port. So in case there is a wildcard regular expression being
used on level 1 or 2 below the mapping entry root, this entry should still be
considered for both incoming and outgoing mapping.
> Allow wildcards within hostname, port and scheme to be used and still use the
> entry for reverse mapping
> -------------------------------------------------------------------------------------------------------
>
> Key: SLING-5672
> URL: https://issues.apache.org/jira/browse/SLING-5672
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.4.10
> Reporter: Konrad Windszus
>
> Currently if any wildcards are used in the regular expressions for the Root
> Mapping Entries
> (http://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#root-level-mappings)
> the entry is only considered for {{ResourceResolver.resolve(...)}}, i.e.
> inward mapping but no longer for {{ResourceResolver.map(...)}}, i.e. outward
> mapping.
> While this makes sense for the {{URL path}} part it would be good to allow
> that for {{scheme}}, {{host}} or {{port}}. So in case there is a wildcard
> regular expression being used on level 1 or 2 below the mapping entry root,
> this entry should still be considered for both inward and outward mapping.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
