The <Path> element is used to apply content rules to requests containing a specific path segment.

Path matching can be nested, and embedding multiple path segments in a single element is also allowed to simplify authoring rules. However, segments between matching portions cannot be skipped, except by using the <PathRegex> element instead.

Path matching is also greedy. As much of the request's path as possible is consumed during each comparison, and only the remaining portion is used in any subequent nested comparison.

Finally, do not attempt to use a <Path> element with only a "/" character to indicate the root of a virtual host. It will be ignored, and your log will contain a warning. Put any settings that apply to a virtual host in the parent <Host> element.

Attributes

Content Specifiers

Names

Type

Description

name string

Required attribute, specifies a path segment to match against. Lower case must be used, and case sensitive matching is not permitted. Multiple segments can be included by using slashes to separate them.

Content Settings

XML attributes corresponding to request mapper properties are used.

Child Elements

Access Control 

Nested Content Specifiers

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>