Show search and navigation.
Purpose: Identifies requests by whether the requested URL points to a relative path that matches a literalThis type of value does not assign a special meaning to characters. The only exception is % which is used for URL encoding. value. This relative path includes the filename of the requested assetA file is the most commonly known example of an asset. Refers to any collection of data that is typically stored as a single unit on a storage unit (e.g., disk drive). An example of an asset that is not physically stored on a disk drive occurs when dynamically generated content is not cached..
The Relative to option determines whether the URL comparison will start before or after the content access pointThis URL segment of a CDN URL identifies where the request should be directed. This relative path starts directly after the CDN hostname. The proper syntax for a content access point is "/yyAN," where "yy" stands for the origin identifier and "AN" stands for a customer account number. A content access point for a customer origin also includes a directory that identifies it..
The content access point is the portion of the path that appears between the CDN hostname and the relative path to the requested asset (e.g., /800001/CustomerOrigin). It identifies a location by server type (e.g., CDN or customer origin) and your customer account number.
The available values for this option are explained below.
Root: Indicates that the URL comparison will start directly after the CDN hostname.
Origin: Indicates that the URL comparison will start after the content access point (e.g., /000001 or /800001/myorigin).
An edge CNAME URL will be rewritten to a CDN URL prior to URL comparison.
Both of the following URLs point to the same asset and therefore have the same URL path.
Edge CNAME URL:
URL path (Relative to Root):
URL path (Relative to Origin):
The value associated with this match condition may be defined using any combination of numbers, letters, and/or symbols. All characters, with the exception of the % symbol, will be treated as a fixed value and cannot take on a special meaning.
Replace spaces in the URL path with %20.
Matching against URLs that contain non-US-ASCII characters requires that you specify encoded Unicode characters (e.g., %E3%81%93).
Encode all Unicode characters before setting the Value option. This match condition only accepts encoded Unicode characters.
You should include the following characters instead of こんにちは when defining this match condition's value:
The majority of user agents (e.g., web browsers) encode non-US-ASCII characters in the
Use the Encoded option to determine whether your match value, as defined in the Value option, will be decoded prior to comparison with the request's URL path.
Standard: Use the default configuration (i.e., No) which allows our service to decode your match value.