NestedContentSpecifiers

The following elements are supported to narrow the matching process:

Name	Cardinality	Description

Name	Cardinality	Description
<Path>	0 or more	Matches requests whose first path component is an exact match
<PathRegex>	0 or more	Matches requests whose remaining path as a whole matches a regular expression
<Query>	0 or more	Matches requests containing a matching query string parameter

The further matching is done 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 sibling elements will be tested for a match. Thus, sibling elements cannot overlap in the web space.

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

Service Provider 3

NestedContentSpecifiers

Analytics

Related content