[ 
https://issues.apache.org/jira/browse/SLING-12731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939700#comment-17939700
 ] 

Konrad Windszus commented on SLING-12731:
-----------------------------------------

[~sseifert] What about {{useForNonMatchingHosts}}? Any other suggestions?

> Resource Resolver Mapping: Support multi domains for same path by using 
> primary and secondary mappings
> ------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-12731
>                 URL: https://issues.apache.org/jira/browse/SLING-12731
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>            Reporter: Konrad Windszus
>            Priority: Major
>
> This is a proposal on how to solve the issue described in SLING-1421. 
> Currently if there are multiple resource based mappings for one repository 
> path is is not predictable which one is used. My proposal is to add a 
> "primary" mapping for each repository path, which is used when there is no 
> host header match for the current request (or mapping without considering the 
> request is used). The other mappings are only used in case the 
> host/protocol/scheme matches the HOST header.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to