Use these settings to enhance delivery performance and optimize how the Akamai edge interacts with your origin and end users. The caching templates manage how content is cached at the Akamai edge and within end-user browsers. Effective caching reduces origin load, saves bandwidth, and places assets closer to your users for faster delivery.

Cache Key Query Parameters

This setting determines how Akamai uses a URL's query string to identify and differentiate objects in the cache. Controlling which parameters are included in the "cache key" helps optimize your cache hit ratio and ensures users receive the correct version of a resource.

Option	Description
Include all parameters (preserve order from request)	Selected by default, this setting uses the entire query string exactly as it appears in the request to define the cache key.
Include all parameters (reorder alphabetically)	Includes all parameters but reorders them alphabetically. This increases cache hits by treating ?a=1&b=2 and ?b=2&a=1 as the same object.
Exclude all parameters	Removes all parameters from the cache key of the query string.
Include only specified parameters...	Only the parameters you list are used for the cache key; all others are ignored. This is ideal for including only essential content-identifying IDs.
Exclude only specified parameters...	Removes specific parameters (such as marketing trackers or session IDs) from the cache key while including all other parts of the query string.

To learn more, see Cache Key Query Parameters.

Quick Retry

Enabled by default, this setting detects slow forward throughput while fetching a delivery object and attempts a different forward connection path to avoid congestion.

To learn more, see Quick Retry.

HTTP/3

Enabled by default with no additional settings required.

HTTP/3 reduces latency by replacing TCP with the IETF QUIC protocol. This allows for faster connection setup and more efficient stream handling.

Requirements

To support HTTP/3, make sure you use Transport Layer Security (TLS) 1.3 for client-to-edge requests.

To learn more, see HTTP/3.