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.
Filter requests that originate from a particular:
The available types of match conditions are:
The Always match condition is designed to apply a default set of features to all requests.
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:
|
Device OS |
Identifies requests by whether the device's OS matches a:
|
Device OS Version |
Identifies requests by whether the device's OS version matches a:
|
Identifies requests by whether the device supports dual orientation. |
|
HTML Preferred DTD |
Identifies requests by whether the device's HTML preferred DTD matches a:
|
Identifies requests by whether the device supports Base64 encoded images. |
|
Identifies requests by whether the device uses the Android OS. |
|
Identifies requests by whether a native application requested content. |
|
Identifies requests by whether the device provides a full desktop experience. |
|
Identifies requests by whether the device uses iOS. |
|
Identifies requests by whether the device is considered to be an automated HTTP client (e.g., a robot crawler). |
|
Identifies requests by whether the device is a smart TV. |
|
Identifies requests by whether the device is a smartphone. |
|
Identifies requests by whether the device is a tablet. |
|
Identifies requests by whether the device's primary pointing device is a touchscreen. |
|
Identifies requests by whether the device is a a Windows Mobile 6.5/Windows Phone 7 or higher. |
|
Identifies requests by whether the device is wireless. |
|
Marketing Name |
Identifies requests by whether the device's marketing name matches a:
|
Mobile Browser |
Identifies requests by whether the device's browser matches a:
|
Mobile Browser Version |
Identifies requests by whether the device's browser version matches a:
|
Model Name |
Identifies requests by whether the device's model name matches a:
|
Identifies requests by whether the device supports progressive download. |
|
Release Date |
Identifies requests by whether the device's release date matches a:
|
Identifies requests by the device's height. |
|
Identifies requests by the device's width. |
These match conditions are designed to identify requests based on the requesterRefers to the user that requested content.'s location.
Name | Purpose |
---|---|
Identifies requests that originate from a particular network. |
|
City Name |
Identifies requests by whether they originate from a city whose name matches a:
|
Identifies requests that originate from the specified continents. |
|
Identifies requests that originate from the specified countries. |
|
Identifies requests that originate from the specified metros (Designated Market Areas). |
|
Identifies requests that originate from the specified latitudes. |
|
Identifies requests that originate from the specified longitudes. |
|
Identifies requests that originate from the specified metros (Designated Market Areas). |
|
Identifies requests that originate from the specified postal codes. |
|
Identifies requests that originate from the specified regions. |
Both of these match conditions provide the same capability. However, we recommend the use of the Metro Code match condition to identify requests by DMA.
These match conditions are designed to identify requests that point to CDN storage or a customer origin server.
Name | Purpose |
---|---|
Identifies requests for content stored on CDN storage. |
|
Identifies requests for content stored on a specific customer origin server. |
These match conditions are designed to identify requests based on their properties.
Name | Purpose |
---|---|
Identifies requests that originate from a particular IP address. |
|
Cookie Parameter |
Identifies a request by whether it contains a cookie that matches a:
|
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:
|
Request Header |
Identifies a request by whether it contains a header that matches a:
|
Identifies requests by their HTTP method. |
|
Identifies requests by their HTTP protocol. |
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:
|
URL Path Directory |
Identifies requests by whether their relative path matches a:
|
URL Path Extension |
Identifies requests by whether their file extension matches a:
|
URL Path Filename |
Identifies requests by whether their filename matches a:
|
URL Query |
Identifies requests by whether their query string matches a:
|
URL Query Parameter |
Identifies requests by whether they contain a query string parameter set to a value that matches a:
|
Edgecast CDN