This behavior controls whether the query string or portions of it are used to differentiate objects in cache.
This behavior is automatically included in the Default Rule for a property configuration for AMD. Unlike other behaviors that are automatically included in this rule, it's not required. While we recommend you set it in the Default Rule, so that it will apply to all requests, you can remove it from this rule.
Before you work with this behavior and all caching-related behaviors, Akamai recommends that you read, What you need to know about caching in the Property Manager help. It'll help you better understand caching and how it works within the Akamai network.
The default setting for this behavior is Exclude all parameters. This means that all requests for the same URL are served from a single cache entry regardless of the query string in a request. For example, these two requests would be served from the same object in cache:
This setting tells Akamai to only consider the URL without the query string when looking in the cache. Using the examples above, that would be:
Is the default Exclude all parameters setting appropriate for your content? If not, pick the appropriate setting for your environment to have Akamai optimize delivery by incorporating use case-based provisioning.
NetStorage doesn't honor query strings
If you're using it as your origin server, this needs to be set to Exclude all parameters.
Other available options include:
Include all parameters (preserve order from request)
All of the query string parameters in a request are included, and they're applied in the order they exist in the request.
Include all parameters (reorder alphabetically)
All of the query string parameters in a request are included, but they're reordered alphabetically and then applied.
Include only specified parameters...
Only specific query strings are included, and all others are ignored.
Enter the query string parameters you want included in the cache key. Matches are determined by prefix-matching each query string. If the query parameter with its value (
To honor a query string in a request, its name needs to be exactly what's set in Parameters. For example, if you input
The individual strings you set in Parameters are included for a request if their name matches a portion of the name in the actual request. For example, assume you included
Exclude only specified parameters
Specific query strings are excluded, and all others are applied.
Enter the query string parameters you want excluded from the cache key. Matches are determined by prefix matching each query string. If the query parameter with its value (
To exclude a query string from a request, its name needs to be exactly what's set in Parameters. For example, if you enter
The individual strings you set in Parameters are excluded from a request if their name matches a portion of the name in the actual request. For example, assume you included
If you change the cache key globally or for too many objects on a property that is already active—that is, if you create a new version that has a different cache key for all content—you can create problems for your origin when you activate the new version on production. When you change the cache key, you invalidate cached content that's using the existing cache key. Akamai edge servers will request new objects from your origin at a level that can create severe spikes in bandwidth.
If you need to change the cache keys on an active configuration, you should limit the changes: send them out a few changes at a time over an expanded time frame.
Updated 9 months ago