URL Path Wildcard

Purpose: Compares a request's relative path to the specified pattern.

An option is provided to indicate whether this condition will be met when the exact 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. A 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 (i.e., CDN or customer origin) and your user account (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) specified in the parent "CDN Origin" or "Customer Origin" match.
• 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/asset.htm
  • URL path (Origin): /path/asset.htm
  Edge CNAME URL: http://my.domain.com/path/asset.htm
  • URL path (Root): /800001/CustomerOrigin/path/asset.htm
  • URL path (Origin): /path/asset.htm
• Specify multiple URL paths by delimiting each one with a single space. Sample syntax is provided below.
  /marketing/asset.*/sales/*.htm
• Only exact URL matches to at least one of the specified patterns will satisfy this condition.
• For the purpose of satisfying this condition, query strings in the URL are ignored.
• The case-sensitivity of URL comparisons is determined by the Ignore Case option.
• Spaces in the URL path should be replaced with "%20."
• The value specified for 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.

Tip: If you would like to see the applicable content access points for your account, please select either the "CDN Origin" or the "Customer Origin" match options.

Sample Scenarios

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

Value	Relative To	Result
*/test.html */test.php	Root	This pattern will be satisfied by assets named test.html or test.php in any folder.
/80ABCD/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 text folder.
*/css/* */js/*	Root	This pattern will be satisfied by all CDN or edge CNAME URLs containing a css or js folder.
*.jpg *.gif *.png	Root	This pattern will be satisfied by all CDN or edge CNAME URLs ending with .jpg, .gif, or .png. An alternative way to specify this pattern is the "URL Path Extension" match option.
/images/* /media/*	Origin	This pattern will be satisfied by all edge CNAME URLs that contain an "images" or "media" folder directly after the content access point. Reminder: Setting the Relative To option to "Origin" requires that this match option be nested under a CDN Origin or Customer Origin match option.