Match Conditions

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.

A matchRules Engine: Defines a prerequisite that must be met before one or more actions (i.e., features) may be applied to a request. condition identifies specific types of requests for which a set of features will be performed.

Learn more.

The available types of match conditions are:

Always
Device
Location
Origin
Request
URL

Always

The Always match condition is designed to apply a default set of features to all requests.

Device

These match conditions are designed to identify requests based on the client's user agent.

Name	Purpose
Brand Name	Identifies requests by whether the device's brand name matches a: Specific value (Brand Name Literal) Regular expression (Brand Name Regex) Specific pattern (Brand Name Wildcard)
Device OS	Identifies requests by whether the device's OS matches a: Specific value (Device OS Literal) Regular expression (Device OS Regex) Specific pattern (Device OS Wildcard)
Device OS Version	Identifies requests by whether the device's OS version matches a: Specific value (Device OS Version Literal) Regular expression (Device OS Version Regex) Specific pattern (Device OS Version Wildcard)
Dual Orientation?	Identifies requests by whether the device supports dual orientation.
HTML Preferred DTD	Identifies requests by whether the device's HTML preferred DTD matches a: Specific value (HTML Preferred DTD Literal) Regular expression (HTML Preferred DTD Regex) Specific pattern (HTML Preferred DTD Wildcard)
Image Inlining?	Identifies requests by whether the device supports Base64 encoded images.
Is Android?	Identifies requests by whether the device uses the Android OS.
Is App?	Identifies requests by whether a native application requested content.
Is Full Desktop?	Identifies requests by whether the device provides a full desktop experience.
Is iOS?	Identifies requests by whether the device uses iOS.
Is Robot?	Identifies requests by whether the device is considered to be an automated HTTP client (e.g., a robot crawler).
Is Smart TV?	Identifies requests by whether the device is a smart TV.
Is Smartphone?	Identifies requests by whether the device is a smartphone.
Is Tablet?	Identifies requests by whether the device is a tablet.
Is Touchscreen?	Identifies requests by whether the device's primary pointing device is a touchscreen.
Is Windows Phone?	Identifies requests by whether the device is a a Windows Mobile 6.5/Windows Phone 7 or higher.
Is Wireless Device?	Identifies requests by whether the device is wireless.
Marketing Name	Identifies requests by whether the device's marketing name matches a: Specific value (Marketing Name Literal) Regular expression (Marketing Name Regex) Specific pattern (Marketing Name Wildcard)
Mobile Browser	Identifies requests by whether the device's browser matches a: Specific value (Mobile Browser Literal) Regular expression (Mobile Browser Regex) Specific pattern (Mobile Browser Wildcard)
Mobile Browser Version	Identifies requests by whether the device's browser version matches a: Specific value (Mobile Browser Version Literal) Regular expression (Mobile Browser Version Regex) Specific pattern (Mobile Browser Version Wildcard)
Model Name	Identifies requests by whether the device's model name matches a: Specific value (Model Name Literal) Regular expression (Model Name Regex) Specific pattern (Model Name Wildcard)
Progressive Download?	Identifies requests by whether the device supports progressive download.
Release Date	Identifies requests by whether the device's release date matches a: Specific value (Release Date Literal) Regular expression (Release Date Regex) Specific pattern (Release Date Wildcard)
Resolution Height	Identifies requests by the device's height.
Resolution Width	Identifies requests by the device's width.

Location

These match conditions are designed to identify requests based on the requesterRefers to the user that requested content.'s location.

Name	Purpose
AS Number	Identifies requests that originate from a particular network.
City Name	Identifies requests by whether they originate from a city whose name matches a: Specific value (City Name Literal) Regular expression (City Name Regex)
Continent	Identifies requests that originate from the specified continents.
Country	Identifies requests that originate from the specified countries.
DMA Code	Identifies requests that originate from the specified metros (Designated Market Areas).
Latitude	Identifies requests that originate from the specified latitudes.
Longitude	Identifies requests that originate from the specified longitudes.
Metro Code	Identifies requests that originate from the specified metros (Designated Market Areas).
Postal Code	Identifies requests that originate from the specified postal codes.
Region Code	Identifies requests that originate from the specified regions.

Origin

These match conditions are designed to identify requests that point to CDN storage or a customer origin server.

Name	Purpose
CDN Origin	Identifies requests for content stored on CDN storage.
Customer Origin	Identifies requests for content stored on a specific customer origin server.

Request

These match conditions are designed to identify requests based on their properties.

Name	Purpose
Client IP Address	Identifies requests that originate from a particular IP address.
Cookie Parameter	Identifies a request by whether it contains a cookie that matches a: Specific value (Cookie Parameter Literal) Regular expression (Cookie Parameter Regex) Specific pattern (Cookie Parameter Wildcard)
Edge CNAME	Identifies requests that point to a specific edge CNAME.
Referring Domain	Identifies a request by whether it was referred by a hostname that matches a: Specific value (Referring Domain Literal) Specific pattern (Referring Domain Wildcard)
Request Header	Identifies a request by whether it contains a header that matches a: Specific value (Request Header Literal) Regular expression (Request Header Regex) Specific pattern (Request Header Wildcard)
Request Method	Identifies requests by their HTTP method.
Request Scheme	Identifies requests by their HTTP protocol.

URL

These match conditions are designed to identify requests based on their URLs.

Name	Purpose
URL Path	Identifies requests by whether their relative path, including filename, matches a: Specific value (URL Path Literal) Regular expression (URL Path Regex) Specific pattern (URL Path Wildcard)
URL Path Directory	Identifies requests by whether their relative path matches a: Specific value (URL Path Directory Literal) Specific pattern (URL Path Directory Wildcard)
URL Path Extension	Identifies requests by whether their file extension matches a: Specific value (URL Path Extension Literal) Specific pattern (URL Path Extension Wildcard)
URL Path Filename	Identifies requests by whether their filename matches a: Specific value (URL Path Filename Literal) Specific pattern (URL Path Filename Wildcard)
URL Query	Identifies requests by whether their query string matches a: Specific value (URL Query Literal) Regular expression (URL Query Regex) Specific pattern (URL Query Wildcard)
URL Query Parameter	Identifies requests by whether they contain a query string parameter set to a value that matches a: Specific value (URL Query Parameter Literal) Specific pattern (URL Query Parameter Wildcard)