URL Path Regex

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.

ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior. - Advanced

This capability requires Rules Engine - Advanced Rules which must be purchased separately. Contact your CDN account manager to activate it.

Category: URL

Purpose: Identifies requests by whether the requested URL points to a relative path that matches the pattern defined by a Perl-compatible regular expressionThis type of value is interpreted as a regular expression that defines a pattern of characters.. 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..

Choosing the right URL path match condition.

Key information:

An edge CNAME URL will be rewritten to a CDN URL prior to URL comparison.

Example:

Both of the following URLs point to the same asset and therefore have the same URL path.

CDN URL:

http://wpc.0001.omegacdn.net/800001/CustomerOrigin/path/asset.htm

Edge CNAME URL:

http://my.domain.com/path/asset.htm

URL path:

/800001/CustomerOrigin/path/asset.htm
A value may be defined using any combination of numbers, letters, and/or symbols. This value will be interpreted as a regular expression. Regular expressions are useful for defining a pattern of characters.

Although regular expressions are quite powerful and can generate flexible solutions, it is strongly recommended that a regular expression statement be constructed, or at the very least proofed, by a developer on your team. This will ensure that the desired behavior will take place.

For example, specifying a ".*" regular expression will match all requests, since the specified pattern matches 0 or more characters. A clearer way to match all requests is through the use of the Always match 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.
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.
  
  Example:
  
  You should include the following characters instead of こんにちは when defining this match condition's value:
  
  %E3%81%93%E3%82%93%E3%81%AB%E3%81%A1%E3%81%AF
- The majority of user agents (e.g., web browsers) encode non-US-ASCII characters in the request URL before submitting the request to our CDN. By default, our CDN service then decodes those characters before the comparison for this match condition is performed.
- 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.
  - URL Normalization: You must set this option to Yes when a URL normalization customization has been applied to your traffic. This configuration ensures that your match value remains encoded.
  - Standard: Use the default configuration (i.e., No) which allows our service to decode your match value.
This match condition is satisfied when the relative URL path is either an exact match (i.e., match) or does not match the regular expression.