Release Date Wildcard

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. - Mobile Device Detection Rules

This match condition requires Rules Engine - Mobile Device Detection Rules. This component of Rules Engine must be purchased separately. Contact your CDN account manager to activate it.

Category: Device

Purpose: Identifies requests by whether the device that issued the request was added to the WURFL database on a date (e.g., 2013_december) that 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.

Format:

yyyy_mmIdentifies a month in lower-case letters.

Key information:

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.
Specify multiple values by delimiting each one with a single space.
The Ignore Case option determines whether a case-sensitive comparison will be made against the specified value.
The Result option determines whether this match condition will be met when the device's WURFL release date is a "match" or does not match the specified pattern.
Due to the manner in which cache settings are tracked, this match condition is incompatible with the following features:
- Complete Cache Fill (End-of-Life)
- Default Internal Max-Age
- Force Internal Max-Age
- Ignore Origin No-Cache
- Internal Max-Stale