[
https://issues.apache.org/jira/browse/SLING-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939617#comment-17939617
]
Konrad Windszus commented on SLING-5672:
----------------------------------------
The problem with having wildcards in either host, scheme or port is that then
it is no longer possible to construct the absolute URL (which is crucial for
cross-site/domain linking).
> 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
> Priority: Major
>
> 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/reverse 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
(v8.20.10#820010)
