Request Header Wildcard

Category: Request

Purpose: Identifies requests by whether they contain a request header whose value matches a pattern defined by a wildcardThis type of value supports the use of special characters to establish a pattern. For example, specifying an asterisk within this type of value will match one or more characters. 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 value(s) associated with this match condition may be defined using any combination of numbers, letters, and/or symbols. This type of value also supports the use of special characters.

    Each specified value may contain one or more asterisks. Each asterisk will match a sequence of one or more characters.

  • The case-sensitivity of header value comparisons is determined by the Ignore Case option.
  • Replace spaces in the header value with %20.
  • Specify multiple values by delimiting each one with a single space.

• The Result option determines the conditions under which this match condition will be satisfied.

  • Match: Requires the request to contain the specified header and its value must match at least one of the patterns defined in this match condition.

  • Does Not Match: Requires that the request satisfy either of the following criteria:

    • It does not contain the specified header.
    • It contains the specified header, but its value does not match one of the patterns defined in this match condition.

• Due to the manner in which cache settings are tracked, this match condition is incompatible with the following features:

  • Default Internal Max-Age
  • Force Internal Max-Age
  • Ignore Origin No-Cache
  • Internal Max-Stale

Sample Scenarios

Sample scenarios are provided below.

The following sample configurations assume that this match condition is satisfied when a request matches one of the specified values.

Header Name	Header Value	Description
Referer	http://www.domain.com/	This configuration will match a request with the following request header: Referer: http://www.domain.com/ It will not match a request with the following request header: Referer: http://www.domain.com/page.php
Referer	http://www.domain.com/* http://blog.domain.com/*	These patterns will match requests from any referring URL from either of the following: http://www.domain.com/ http://blog.domain.com/
User-Agent	*Mozilla/5.0 *Android 4.0.4*	This pattern will match requests whose user agent contains the following string: Mozilla/5.0 (Linux; U; Android 4.0.4;

Edgecast CDN