Host

The <Host> element is used to apply content rules to requests to a specific virtual host (or often to the two virtual hosts running on the default ports).

Attributes

Content Specifiers

Names	Type	Description
`name`	string	Required attribute, specifies the hostname of requests to match against. This must correspond to the "canonical" name of the virtual host, or the client can circumvent the matching process.
`scheme`	"`http`", "`https`"	Optional scheme of requests to match against. Used to match only requests using a specific protocol. If omitted, any protocol will be matched.
`port`	integer	Optional port of requests to match against. Used to match only requests using a specific port. If omitted, any request to the default port for the protocol used (either 80 or 443) will be matched

Content Settings

XML attributes corresponding to request mapper properties are used.

Child Elements

Access Control

One of the following child elements can be used to attach an access control policy to matching requests:

<htaccess>
- Enables native Apache .htaccess support during Apache's authorization phase. This is automatic and implicitly plugged in for the Native RequestMapper, but can be enabled by hand if the XML RequestMapper is used. Note that this will fail for non-Apache servers.

<AccessControlProvider>
- Attaches a custom access control implementation provided by a plugin

<AccessControl>
- Attaches an access control policy using the XML-based plugin provided with the SP. This is a short-hand for embedding the policy in the element above, if you want the policy inside the RequestMapper's configuration file anyway.

If no element is included (or inherited or implicitly enabled), any access control is left to the resource itself and the SP simply passes its session information along.

If an error occurs when processing this element, a dummy policy to deny access is installed to prevent accidental exposure.

Nested Content Specifiers

Unable to render {include} The included page could not be found.