URL Path Directory

Purpose: Identifies requests by their relative path.

For the purposes of this match option, this relative path does not include the filename of the requested asset. An option is provided to indicate whether this condition will be met when the URL path "Matches" or "Does Not Match" one of the specified URL patterns.

Learn more about the core differences between the various URL path match options.

Key information:

• The Relative to option determines whether the URL comparison will start before or after the content access point. The content access point is the portion of the path that appears between the CDN hostname and the relative path to the requested asset. It identifies a location by server type (e.g., CDN or customer origin) and your customer account number (e.g., /800001/CustomerOrigin). The available values for this option are explained below.
  • Root: This value indicates that the URL comparison will start directly after the CDN hostname (e.g., http://wpc.0001.{Base Domain}). This is the default value for this option.
  • Origin: This value is only supported when this match option has been nested under a "CDN Origin" or "Customer Origin" match. This type of configuration indicates that the URL comparison will start after the content access point (e.g., /000001 or /800001/myorigin) specified in the parent "CDN Origin" or "Customer Origin" match option.
• A URL comparison ends right before the filename of the requested asset. A trailing forward slash is the last character in this type of path.
• An edge CNAME URL will be rewritten to a CDN URL prior to URL comparison. In the following example, both URLs point to the same asset and therefore have the same URL path.
  CDN URL: http://wpc.0001.{Base Domain}/800001/CustomerOrigin/path/asset.htm
  • URL path (Root): /800001/CustomerOrigin/path/
  • URL path (Origin): /path/
  Edge CNAME URL: http://my.domain.com/path/asset.htm
  • URL path (Root): /800001/CustomerOrigin/path/
  • URL path (Origin): /path/
• Spaces in the URL path should be replaced with "%20."
• Specify multiple URL paths by delimiting each one with a single space. Sample syntax is provided below.
  */sales/ */marketing/
• A URL path can take advantage of special characters.
• Each URL path pattern can consist of one or more asterisks. Each asterisk will match a sequence of one or more characters.
• If a wildcard character (i.e., *) has not been specified, then only an exact match will satisfy this match option. For example, a match will not be found when the above URLs are requested if this match option is configured to look for any of the following values:
  • /pa
  • /pat
  • ath/
  • /path
• The case-sensitivity of URL comparisons is determined by the Ignore Case option.

Sample Scenario

The following example demonstrates how this option works in specific situations:

Value	Relative To	Result
*/Location1/ */Location2/	Root	This pattern will be satisfied when the parent folder for the requested asset is called either "Location1" or "Location2."
/800001/origin/text/*	Root	This pattern will be satisfied by all CDN URLs that start with the CDN hostname followed by "/80ABCD/origin/text/." This includes all assets and subfolders recursively under the images folder.
*/css/* */js/*	Root	This pattern will be satisfied by all CDN or edge CNAME URLs containing a css or js folder.
/images/* /media/*	Root	This pattern will be satisfied by all edge CNAME URLs that contain an "images" or "media" folder directly after the hostname.
*css* *js* *images* *media*	Root	This pattern will be satisfied by all URLs that contain any of the following words in the relative folder path: css, js, images, or media. The following sample URL path would be a match for this criteria due to the presence of "js": /jsmith/folder1