...
Nested Content Specifiers
Use these "overrides" to match specific content on the virtual host can be included.
...
Name
...
Cardinality
...
Description
...
Matches requests whose first path component is an exact match for the element.
...
Matches requests with a path that matches the element's expression.
...
Matches requests containing a query string parameter satisfying the element.
Matching is done within a <HostRegex> element as follows:
- First, by examining
<Path>elements in order. - Then, by checking any
<PathRegex>elements in order against the part of the path that was not matched in the first step. - 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 HowToRequestMap
| Include Page | ||||
|---|---|---|---|---|
|