Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
Description
Using MatchOrder=host_uri in combination with default siteaccess disables access to content with urls beginning with a part of a configured siteaccess:
Given the following setup:
- 3 Siteaccesses, with one Default Siteaccess and different ContentRootNodeIds
- one Siteaccess is loaded by host_uri-Match
- an Article in the default siteaccess' Subtree Called "content is king"
[SiteSettings] DefaultAccess=default [SiteAccessSettings] AvailableSiteAccessList[] AvailableSiteAccessList[]=default AvailableSiteAccessList[]=content AvailableSiteAccessList[]=content_mobile MatchOrder=host_uri;uri URIMatchType=element HostUriMatchMethodDefault=start HostUriMatchMapItems[] HostUriMatchMapItems[]=m.;content;content_mobile
Currently, the HostUri-Matching is greedy concerning hyphens, so it a call to:
http://m.example.com/content-is-king
ends up in the content_mobile-Siteaccess, displaying an error page.
Expected behavoir would be to display the article in the default siteaccess.