Cookie Parameter Regex

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. - Advanced

This capability requires Rules Engine - Advanced Rules which must be purchased separately. Contact your CDN account manager to activate it.

Category: Request

Purpose: Identifies requests by whether they contain a cookie whose value matches the pattern defined by a Perl-compatible regular expressionThis type of value is interpreted as a regular expression that defines a pattern of characters..

Key information:

Cookie name:
- Special characters, including an asterisk, are not supported when specifying a cookie name. This means that only exact cookie name matches are eligible for comparison.
- Only a single cookie name may be specified per instance of this match condition.
- Cookie name comparisons are case-insensitive.
Cookie value:
- A value may be defined using any combination of numbers, letters, and/or symbols. This value will be interpreted as a regular expression. Regular expressions are useful for defining a pattern of characters.
  
  Although regular expressions are quite powerful and can generate flexible solutions, it is strongly recommended that a regular expression statement be constructed, or at the very least proofed, by a developer on your team. This will ensure that the desired behavior will take place.
  
  For example, specifying a ".*" regular expression will match all requests, since the specified pattern matches 0 or more characters. A clearer way to match all requests is through the use of the Always match condition.
- The Ignore Case option determines whether a case-sensitive comparison will be made against the request's cookie value.
The Result option determines the conditions under which this match condition will be satisfied.
- Match: Requires a request to contain the specified cookie with a value that matches the regular expression defined in this match condition.
- Does Not Match: Requires that the request satisfy either of the following criteria:
  - It does not contain the specified cookie.
  - It contains the specified cookie, but its value does not match the regular expression defined in this match condition.
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