Category: Caching
Purpose: Determines whether the cache-keyA relative path that uniquely identifies an asset for the purpose of caching. Our edge servers use this relative path when checking for cached content and when caching content. By default, a cache-key will not contain query string parameters. will include or exclude query string parameters associated with a request.
Key information:
Specify one or more query string parameter name(s) that will either be included or excluded from the cache-key.
Specify multiple parameters by delimiting each name with a single space.
This feature determines whether query string parameters will be included or excluded from the cache-key. Additional information is provided for each option below.
| Type | Description |
|---|---|
|
Include |
Indicates that each specified parameter should be included in the cache-key. A unique cache-key will be generated for each request that contains a unique value for a query string parameter defined in this feature. |
|
Include All |
Indicates that a unique cache-key will be created for each request to an asset that includes a unique query string. This type of configuration is not typically recommended since it may lead to a small percentage of cache hits. This will increase the load on the origin server, since it will have to serve more requests. This configuration duplicates the caching behavior known as "unique-cache" on the Query-String Caching page. |
|
Exclude |
Indicates that only the specified parameter(s) will be excluded from the cache-key. All other query string parameters will be included in the cache-key. |
|
Exclude All |
Indicates that all query string parameters will be excluded from the cache-key. This configuration duplicates the default caching behavior, which is known as "standard-cache" on the Query-String Caching page. |
The power of Rules Engine allows the customization for the implementation of query string caching. For example, query string caching may be configured to only apply to certain locations or file types.
Duplicate the query string caching behavior known as "no-cache" on the Query-String Caching page by creating a rule that contains a URL Query Wildcard match condition and a Bypass Cache feature. The URL Query Wildcard match condition should be set to an asterisk (*).
Sample usage for this feature is provided below. A sample request and the default cache-key are provided below.
Sample configuration:
This type of configuration would generate the following query string parameter cache-key:
Sample configuration:
This type of configuration would generate the following query string parameter cache-key:
Sample configuration:
This type of configuration would generate the following query string parameter cache-key:
Sample configuration:
This type of configuration would generate the following query string parameter cache-key: