Conditions Reference

A match condition identifies the set of requests to which one or more feature(s) will be applied. The available match conditions are listed below.

Category	Match Conditions
Location	ASN City Country DMA Code Latitude Longitude Postal Code Region Code
Request	Client IP Cookie Filename Method Origin Path Path POP Code Query Query Parameter Query String Referring Domain Request Header Scheme
Device	Brand Name Dual Orientation Image Inlining Is Android Is App Is iOS Is Robot Is Smartphone Is SmartTV Is Tablet Is Touchscreen Is Windows Phone Is Wireless Device Marketing Name Mobile Browser Model Name Progressive Download Release Date Resolution Height Resolution Width
Miscellaneous	Random Integer

ASN

Identifies requests by the network from which the request was issued. A network is identified by its Autonomous System Number (ASN).

Key information:

Certain requests may not return a valid AS number. A question mark (i.e., ?) will match requests for which a valid AS number could not be determined.
Specify a value that matches the entire AS number for the desired network.
Specify multiple AS numbers by delimiting each one with a single space.

Example: A value of 64514 64515 matches requests arriving from either 64514 or 64515.

Brand Name

Identifies requests by the manufacturer (e.g., Samsung) of the device that issued the request.

Key information:

Specify a value using any combination of numbers, letters, or symbols.
The method for specifying multiple values varies by operator:
- equals | does not equal: Delimit each one with a single space (e.g., value1 value2).
  
  Replace spaces in the brand name with %20.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

City

Identifies requests by the city from which they originated.

Key information:

Certain requests may not return a valid city name. A question mark (i.e., ?) will match requests for which a valid city name could not be determined.

Client IP

Identifies requests that originate from a particular IP address.

Key information:

Use CIDR notation.
Specify multiple IP addresses and/or IP address blocks by delimiting each one with a single space.
- IPv4 Example: 1.2.3.4 10.20.30.40 matches any requests arriving from either 1.2.3.4 or 10.20.30.40.
- IPv6 Example: 1:2:3:4:5:6:7:8 10:20:30:40:50:60:70:80 matches any requests arriving from either 1:2:3:4:5:6:7:8 or 10:20:30:40:50:60:70:80.
The syntax for an IP address block is the base IP address followed by a forward slash and the prefix size.
- IPv4 Example: 5.5.5.64/26 matches any requests arriving from 5.5.5.64 through 5.5.5.127.
- IPv6 Example: 1:2:3::0/48 matches any requests arriving from 1:2:3:0:0:0:0:0 through 1:2:3:ffff:ffff:ffff:ffff:ffff.
  
  IPv6 address blocks should not be fully shortened. As shown in the above example, a trailing 0 is required when shortening fields that consist of 0’s.

Identifies requests by a cookie’s value.

Key information:

Set the Cookie Name option to the exact name of the desired cookie. You may not use special characters, including an asterisk, or a regular expression.
Only a single cookie name may be specified per instance of this match condition.
Cookie name comparisons are case-insensitive.
The method for specifying multiple cookie values varies by operator:
- equals | does not equal: Delimit each one with a single space.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Country

Identifies requests by the country from which the request was issued. Specify each desired country through its country code.

Key information:

Specify multiple country codes by delimiting each one with a single space.
The EU and AP country codes do not encompass all IP addresses in those regions.

Learn more.
Certain requests may not return a valid country code. A question mark (i.e., ?) will match requests for which a valid country code could not be determined.
Country codes are case-sensitive.

DMA Code

Identifies requests by the metro code (Designated Market Area - DMA) from which the request was issued.

Key information:

Specify a metro code as an integer value.
Request DMA codes from Nielsen.
Specify multiple metro codes by delimiting each one with a single space.
Metro codes are only applicable for traffic from the United States.
Certain requests may not return a valid metro code. A question mark (i.e., ?) will match requests for which a valid metro code could not be determined.

Dual Orientation

Identifies requests by whether the device that issued the request supports dual orientation (i.e., portrait and landscape).

Extensions

Identifies requests by the file extension defined in the URL.

This match condition looks for a URL that ends with a period (.) and the specified file extension. Therefore, make sure that any file extensions specified in the Value option do not contain a leading period.

Correct: htm

Incorrect: .htm

Filename

Identifies requests by the filename defined in the URL.

Key information:

For the purposes of this match condition, a filename consists of the name of the requested asset, a period, and the file extension (e.g., index.html).
The method for specifying multiple values varies by operator:
- equals | does not equal: Delimit each one with a single space.
  
  Replace spaces in the filename with %20.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Image Inlining

Identifies requests by whether the device that issued the request supports Base64-encoded images.

Is Android

Identifies requests by whether the operating system of the device that issued the request is Android.

Is App

Identifies requests by whether the device that issued the request is a native application.

Is iOS

Identifies requests by whether the operating system of the device that issued the request is iOS.

Is Robot

Identifies requests by whether the device that issued the request is considered to be an automated HTTP client (e.g., a robot crawler).

Is Smartphone

Identifies requests by whether the device that issued the request is a smartphone.

Is SmartTV

Identifies requests by whether the device that issued the request is a smart TV.

Is Tablet

Identifies requests by whether the device that issued the request is a tablet. This is an OS-independent description.

Is Touchscreen

Identifies requests by whether the device that issued the request uses a touchscreen as the primary pointing device.

Is Windows Phone

Identifies requests by whether the device that issued the request is a Windows Mobile 6.5/Windows Phone 7 or higher.

Is Wireless Device

Identifies requests by whether the device that issued the request is a wireless device.

Latitude

Identifies requests by the latitude from which the request was issued.

Key information:

Latitude is not precise. It returns the geographic coordinate for the postal code, city, region, or country associated with the IP address that submitted the request.
Specify latitude as a decimal value from 0 to 90. Preprend - for negative values.

Example: 33.9705
Certain requests may not return a valid latitude. A question mark (i.e., ?) will match requests for which a valid latitude could not be determined.

Longitude

Identifies requests by the longitude from which the request was issued.

Key information:

Longitude is not precise. It returns the geographic coordinate for the postal code, city, region, or country associated with the IP address that submitted the request.
Specify longitude as a decimal value from 0 to 90. Preprend - for negative values.

Example: -118.4308
Certain requests may not return a valid longitude. A question mark (i.e., ?) will match requests for which a valid longitude could not be determined.

Marketing Name

Identifies requests by the marketing name (e.g., BlackBerry 8100 Pearl) of the device that issued the request.

Key information:

The method for specifying multiple values varies by operator:
- equals | does not equal: Delimit each one with a single space.
  
  Replace spaces in the name with %20.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Method

Identifies requests by their HTTP method. Only assets that are requested using the selected request method will satisfy this condition.

Mobile Browser

Identifies requests by the name of the browser (e.g., Chrome) that issued the request.

Key information:

The method for specifying multiple values varies by operator:
- equals | does not equal: Delimit each one with a single space.
  
  Replace spaces in the browser name with %20.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Model Name

Identifies requests by the model name (e.g., s10) of the device that issued the request.

Key information:

The method for specifying multiple values varies by operator:
- equals | does not equal: Delimit each one with a single space.
  
  Replace spaces in the model name with %20.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Origin Path

Identifies requests by the request URL’s relative path. This relative path comparison is performed on rewritten or redirected URLs.

Key information:

This relative path comparison is performed after Edgio rewrites or redirects the request. Rewrite or redirect a URL through the URL Rewrite and URL Redirect features, respectively. Use the Path match condition to match on the original relative path submitted by the client.
This relative path starts directly after the hostname.
For the purpose of satisfying this condition, query strings in the URL are ignored.
Certain characters require URL encoding. Use the percentage symbol to URL encode the following characters:
- SPACE: %20
- &: %26
- %: %25
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’s query string before submitting the request to our CDN. By default, our CDN service does not decode those characters.
  
  Curl does not encode non-US-ASCII characters.

Path

Identifies requests by the relative path of the request URL submitted by the client.

Key information:

Although you may configure Edgio to rewrite or redirect a URL, this relative path comparision will always be performed against the request URL submitted by the client. Use the Origin Path match condition to match on a rewritten or redirected URL.
This relative path starts directly after the hostname.
For the purpose of satisfying this condition, query strings in the URL are ignored.
Certain characters require URL encoding. Use the percentage symbol to URL encode the following characters:
- SPACE: %20
- &: %26
- %: %25
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’s query string before submitting the request to our CDN. By default, our CDN service does not decode those characters.
  
  Curl does not encode non-US-ASCII characters.

POP Code

Identifies requests by the point-of-presence (POP) that processed the request. Set this match condition to the three-letter code for the desired POP.

Postal Code

Identifies requests by the postal code from which the request was issued.

Key information:

Specify a postal code as an integer value.
A comparison will only be performed against the first 3 characters for Canadian postal codes.
A comparison will only be performed against the first 2 - 4 characters for United Kingdom postal codes.
Certain requests may not return a valid postal code. A question mark (i.e., ?) will match requests for which a valid postal code could not be determined.
The method for specifying multiple values varies by operator:
- equals | does not equal: Delimit each one with a single space.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Progressive Download

Identifies requests by whether the device that issued the request supports the playback of audio/video while it is still being downloaded.

Query

Identifies requests by the query string of the request URL submitted by the client.

Key information:

Although you may configure Edgio to rewrite or redirect a URL, this query string comparision will always be performed against the request URL submitted by the client. Use the Query String match condition to match on a rewritten or redirected URL.
The value associated with this match condition will be compared against the entire request’s query string.
For the purposes of this option, a query string starts with the first character after the question mark (?) delimiter for the query string. Therefore, the text specified in the Value option should not include a leading question mark (?).
Certain characters require URL encoding. Use the percentage symbol to URL encode the following characters:
- SPACE: %20
- &: %26
- %: %25
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’s query string before submitting the request to our CDN. By default, our CDN service does not decode those characters.
  
  Curl does not encode non-US-ASCII characters.

Query Parameter

Identifies requests by the value assigned to a query string parameter in the request URL. This comparison is performed on rewritten or redirected URLs.

Key information:

Parameter name:
- Query parameter name comparisons are case-insensitive.
- Replace spaces in the parameter name with %20.
- Only query parameters whose name is an exact match to the specified value may satisfy this condition.
Parameter value:
- Certain characters require URL encoding. Use the percentage symbol to URL encode the following characters:
  - SPACE: %20
  - &: %26
  - %: %25
- The method for specifying multiple values varies by operator:
  - equals | does not equal: Delimit each one with a single space.
    
    Replace spaces in the value with %20.
  - matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Query String

Identifies requests by the query string of the requested URL. This query string comparison is performed on rewritten or redirected URLs.

Key information:

This query string comparison is performed after Edgio rewrites or redirects the request. Rewrite or redirect a URL through the URL Rewrite and URL Redirect features, respectively. Use the Query match condition to match on the original query string submitted by the client.
The value associated with this match condition will be compared against the entire request’s query string.
For the purposes of this option, a query string starts with the first character after the question mark (?) delimiter for the query string. Therefore, the text specified in the Value option should not include a leading question mark (?).
Certain characters require URL encoding. Use the percentage symbol to URL encode the following characters:
- SPACE: %20
- &: %26
- %: %25
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’s query string before submitting the request to our CDN. By default, our CDN service does not decode those characters.
  
  Curl does not encode non-US-ASCII characters. If you would like to test this match condition using curl, then you will need to create a mutually exclusive match section (i.e., IF / ELSE IF). Each conditional expression within that statement should contain this match condition with the Encoded option set to different values.

Random Integer

Identifies requests by performing a comparison against a random integer.

This condition is useful for applying an action to a random set of requests.

For example, if you set the maximum value to 2, then Edgio will randomly apply 0, 1, and 2 to each request. If you configure this condition to match when the value is greater than 1, then you can apply a set of actions to approximately a third of your requests.

Key information:

This condition generates a random integer between 0 and a user-defined number for each request. Edgio will compare the number assigned to the request to the value defined within this condition.
Define the maximum value for this random number generation through the Random Integer Range (from 0 to ?) option.
Define the value to which Edgio will perform a comparison through the Value option.

Referring Domain

Identifies requests by the referrer’s hostname. A referrer’s hostname is determined by the Referer header.

Key information:

The method for specifying multiple values varies by operator:
- equals | does not equal: Delimit each one with a single space.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Region Code

Identifies requests by the code for the region (e.g., state or province) from which the request was issued.

Key information:

Identify the desired region by its region code. A region code, which consists of 1 to 3 alphanumeric characters, identifies a subdivision of a country by the region segment of the corresponding ISO 3166-2 code.

View ISO 3166-2 codes. (Wikipedia)

View ISO 3166-2 codes. (UNECE)

Example:

The ISO 3166-2 code for California is US-CA. Therefore, the region code for California is CA.
Certain regions have two levels of subdivisions. The specified value will be compared against the most specific region code.

Example:

A request that originates from the Devon (aka Devonshire) county of England, which is part of the United Kingdom (UK), has the following subdivisions: GB and DEV. Requests from this county will be matched against DEV.
Region codes are only unique within a country. In order to prevent false positives, we strongly recommend that you also add the Country match condition to your rule.

Example:

Requests from the following regions will report the same region code (i.e., SP):
- São Paulo, Brazil (BR-SP)
- La Spezia, Italy (IT-SP)
- Sandy Point, Bahamas (BS-SP)
Certain requests may not return a valid region code. A question mark (i.e., ?) will match requests for which a valid region code could not be determined.
The method for specifying multiple values varies by operator:
- equals | does not equal: Delimit each one with a single space.
- matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Release Date

Identifies requests by the date on which the device that issued the request was added to the WURFL database.

Format: <YYYY>_<MM>

Example: 2022_december

Request Header

Identifies requests by request header value.

Key information:

Header name:
- Header name comparisons are case-insensitive.
- Replace spaces in the header name with %20.
- Only request headers whose name is an exact match to the specified value may satisfy this condition.
Header value:
- The method for specifying multiple values varies by operator:
  - equals | does not equal: Delimit each one with a single space.
    
    Replace spaces in the value with %20.
  - matches regular expression | does not match regular expression: Use regular expression syntax (e.g., value 1|value 2).

Resolution Height

Identifies requests by the height, in pixels, of the device that issued the request.

Key information:

Specify height in pixels.
Specify height as a whole number.

Resolution Width

Identifies requests by the width, in pixels, of the device that issued the request.

Key information:

Specify width in pixels.
Specify width as a whole number.

Scheme

Identifies requests by their HTTP protocol: HTTP or HTTPS.