Page Comparison

...

XML attributes corresponding to request mapper properties are used.

Example

 
    <RequestMapper type="Native">
        <RequestMap applicationId="default">
            <Host name="sp.example.org">
                <!-- Example of a single nested path segment -->
                <Path name="secure">
                        <!-- Example of a multiple path segments separated by slashes -->
                        <Path name="/create/new/class" authType="shibboleth" requireSession="true">
                                <AccessControl><NOT><Rule require="affiliation">student</Rule></NOT></AccessControl>
                        </Path>
                </Path>
            </Host>
        </RequestMap>
    </RequestMapper>

Child Elements

Access Control

Nested Content Specifiers

Zero or more of these "overrides" to match specific content deeper inside the matched path can be included.

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

...

Matching is done 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 match on the name attribute 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.