The <HostRegex> element is used to apply content rules to requests to any virtual host that matches a regular expression. The input expression is constructed as:
scheme://hostname:port

Attributes

Content Specifiers

• regex (string)
  • Required attribute, specifies the regular expression to apply.

• ignoreCase (boolean) (defaults to true)
  • Controls case option in regex engine, should be left on in most cases.
  • Deprecated in V2.6.0

Version 2.6 and Above

• caseSensitive (boolean) (defaults to false).
  
  • If false, the case-ignoring option is set for the regular expression engine. 

Content Settings

XML attributes corresponding to request mapper properties are used.

Child Elements

Access Control

Nested Content Specifiers

Zero or more of these "overrides" to match specific content on the virtual host can be included.

• <Path>
  • Matches requests whose first path component is an exact match for the element.

• <PathRegex>
  • Matches requests with a path that matches the element's expression.

• <Query>
  • Matches requests containing a query string parameter satisfying the element.

Matching is done within a <HostRegex> element as follows:

1. First, by examining <Path> elements in order.
2. Then, by checking any <PathRegex> elements in order against the part of the path that was not matched in the first step.
3. Finally, by examining any <Query> elements in order.

Once a matching child element is found, the process steps "into" that element and no other siblings will be applied. Thus, siblings cannot overlap.

For more details on how the request mapping process works, see the request mapper HOWTO.