| Table of Contents |
|---|
Overview
The <Path> element is used to apply content settings to requests containing a specific path segment at a particular point in the complete path.
...
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 an entire virtual host in the parent <Host> element.
Reference
Attributes
Content Specifiers
Names | Type | Req? | Description |
|---|
name name | string | Y | Required, specifies a path segment to match against. Lower case must be used, and case sensitive matching is not supported. Multiple segments can be included by using forward slashes to separate them. |
Content Settings
The element supports a large number of XML attributes corresponding to the content settings supported by the SP:
| Include Page | ||||
|---|---|---|---|---|
|
Child Elements
Access Control
| Include Page | ||||
|---|---|---|---|---|
|
Nested Content Specifiers
| Include Page | ||||
|---|---|---|---|---|
|
Example
The example below demonstrates a couple of different syntaxes, but note that the lack of any settings applied to the "secure" path at the root implies that the nested element could just as easily have been specified as "secure/create/new/class" with the same meaning.
...