> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/caching/query-string-caching.md).

# Query String Caching

The **Query String Caching** feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery.\
It determines how the CDN evaluates query parameters when generating cache keys, allowing you to cache each query string variant separately, ignore specific parameters, or build cache keys using only selected values. These configurations provide granular control over caching behavior for dynamic endpoints, APIs, and personalized content.

For configuration details, caching modes, and examples, refer to the main documentation:\
**Learn more in the** [**Query String Caching documentation**](/products/performance-cdn/static-content-delivery/advanced-configuration/caching/query-string-caching.md)**.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/caching/query-string-caching.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.