> 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/headers/http-strict-transport-hsts-protection.md).

# HTTP Strict Transport (HSTS) Protection

Learn how HSTS Protection enforces HTTPS-only access for dynamic traffic by adding the Strict-Transport-Security header to responses.

The **HSTS Protection** feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery.\
It adds the `Strict-Transport-Security` header to HTTPS responses, instructing browsers to use HTTPS exclusively for a defined period. You can configure max-age, subdomain enforcement, and optional preload parameters to strengthen browser-side security for dynamic applications. This feature does not alter caching behavior, redirect rules, or origin routing.

For configuration details, header parameters, and examples, refer to the main documentation:\
**Learn more in the** [**HSTS Protection documentation**](/products/performance-cdn/static-content-delivery/advanced-configuration/headers/http-strict-transport-hsts-protection.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/headers/http-strict-transport-hsts-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.