Sets the mapping between hostname and siteaccess when using map host-matching.
HostMatchMapItems[]= hostname1; siteaccess1 HostMatchMapItems[]= hostname2; siteaccess2 ...
Each row in the array defines one hostname to match and the siteaccess that will be used for that hostname.
See HostMatchType for examples and more information about host matching.
This documentation stores what it needs to work: a session cookie when you sign in or keep a setting such as the help menu shown or hidden, the design you chose (Classic or Modern) and your language. Only if you agree, it also uses Google Analytics (through Google Tag Manager) to count visits; until then nothing is loaded from Google. Your choice is kept in a cookie for 6 months, and you can change it at any time under "Cookie settings" at the foot of every page. Details are in our Cookie Policy.
The session cookie for signing in and for forms, the cookies that keep your design and language, and the cookie that keeps this choice. They stay on because the website needs them; you can delete them in your browser settings at any time.
Google Analytics, loaded through Google Tag Manager (GTM-MPGWKTQV), counts visits and shows us which pages are read: the pages you open, the page you came from, your browser, device and screen size, and your approximate location derived from your IP address. Google processes the data for us and may transfer it to the USA. It sets the cookies _ga and _ga_* for up to 2 years. Off until you turn it on; when you turn it off again, Google is no longer loaded and these cookies are deleted.
Comments (2 historical)
Written by readers of the earlier documentation sites, kept as they were.
Can more domains be natched to the same siteaccess?
Massimiliano Bariola ·
It should be clarified whether a configuration like this:
i.e. accessing the same siteaccess from many domain names is allowed/feasible or not. This is very useful when waiting for DNS propagation but I had weird behavior from doing that, so I don't know if this operation is disallowed or if I made a mistake elsewhere.
Take care about using port 80 in your urls: itr will not be matched!
Gaetano ·
<i>HostMatchMapItems[]= hostname1; siteaccess1</i>
will not match http://hostname1:80
You will need to add a second rule for that:
<i>HostMatchMapItems[]= hostname1:80; siteaccess1</i>
This might happen not only when entering the url in the browser, but also when using webservices or other http clients that always put the port in the 'Host:' header in the http request.