Property Manager Name: Cache Key Query Parameters
By default, cache keys are formed as URLs with full query strings. This behavior allows you to consolidate cached objects based on specified sets of query parameters.
Note also that whenever you apply behavior that generates new cache keys, your origin server may experience traffic spikes before the new cache starts to serve out.
- behavior (enum string): Configures how sets of query string parameters translate to cache keys:
- IGNORE_ALL causes query string parameters to be ignored when forming cache keys.
- IGNORE or INCLUDE makes the key depend on the sequence of values in the parameters field.
- INCLUDE_ALL_PRESERVE_ORDER forms a separate key for the entire set of query parameters but is sensitive to the order in which they appear. (For example, ?q=akamai&state=ma and ?state=ma&q=akamai cache separately.)
- INCLUDE_ALL_ALPHABETIZE_ORDER forms keys for the entire set of parameters, but the order doesn’t matter. The examples above both use the same cache key.
Be careful when applying behavior not to ignore any parameters that result in substantially different content, as it is not reflected in the cached object.
- parameters (array of string values): With behavior set to INCLUDE or IGNORE, parameters specify the set of parameter field names to include in or exclude from the cache key. By default, these match the field names as string prefixes.
- exactMatch (boolean): When enabled, parameters must match exactly. Keep disabled to match string prefixes.