Query String Caching
Control how query strings affect CDN cache behavior for dynamic or parameterized URLs.
Query String Caching defines how URLs containing query parameters are interpreted by the CDN cache. You can cache each query string variant separately, ignore selected query strings, or build the cache key using only specific parameters.
You can manage Query String Caching in the Medianova Control Panel or via API.
Log in to the Medianova Control Panel, select a CDN resource in the CDN section, and navigate to the Query String Caching section under the Caching tab.
Configure Query String Caching
This workflow defines the primary caching behavior for URLs containing query strings.

Select the Query String Caching Mode
Choose one of the following options under Query String Caching:
On – Cache each query string variant separately.
Off – Ignore all query strings; all variations map to a single cached object.
Request URI – Cache based on the full request URI, including query parameters exactly as received.
Configure Ignore Specific Query Strings
Exclude selected query string parameters so they do not create separate cached variants.
Cache Specific Query Strings Only
Build the cache key using only selected parameters and ignore all others.
Behaviour
On: The CDN caches each unique query string as a separate variant.
Off: Query strings are ignored; all variants map to a single cached object.
Request URI: The full request URI is used as the cache key.
Ignore Specific Query Strings: Excluded parameters do not contribute to the cache key.
Cache Specific Query Strings Only: Only the selected parameters contribute to the cache key; all others are ignored.
FAQ
Do ignored parameters count toward the cache key? No. Ignored parameters never create new cache variants.
Can both Ignore and Cache Specific modes be enabled together? No. Only one mode can be active.
What happens if all modes are Off? All query variations serve the same cached response.
Does enabling On increase cache fragmentation? Yes. Each query combination creates a separate cached object.
Last updated
Was this helpful?