As the original Map/Host matcher, siteaccesses are matched based on the host name, but instead of matching the whole host name, it is checked wether the beginning of the host name matches.
match:
\Cjw\MultiSiteBundle\Matcher\MapHost:
www.example.com: example_user
admin.example.com: example_adminIn this example, these hostname would all resolve to the example_user siteaccess.
As the Map/Host matcher above, this matches on the beginning of the host name and additionally the URI part.
In addition, it features the concept of a default siteaccess. Why this, when we already have a default_siteaccess key in the siteaccess configuration? The reason simple: unlike the standard behaviour, this matcher always appends the URI part, thus eliminating duplication of caches and content.
match:
\Cjw\MultiSiteBundle\Matcher\MapHostURI:
www.example.com/de/(default): example_user_de
www.example.com/en: example_user_en
www.example.net/de: example_net_user_de
www.example.net/en: example_net_user_enIn this example, these hostname result in the following siteaccesses.
- www.example.com -> example_user_de (*)
- www.example.com/de -> example_user_de
- www.example.com/en -> example_user_en
- www.example.net/de -> example_net_user_de
- www.example.net/en -> example_net_user_en
(*) generated routes would be rewritten to include the /de URI part
As the Map/HostURI matcher above, this matches on the beginning of the host name and additionally the URI part.
When no URI part is given, the browser language is used to match instead of the URI part. If no match is found, then the default logic from above is applied.
Identical to Map/HostURI above.