> 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/static-content-delivery/advanced-configuration/http-2.md).

# HTTP/2

Configure HTTP/2 for client-to-CDN connections to improve connection efficiency and reduce latency.

Enable HTTP/2 for client-to-CDN connections to improve connection efficiency and reduce latency.

HTTP/2 allows multiple requests and responses to be transferred over a single connection. When supported by the client, Medianova CDN can use HTTP/2 to reduce connection overhead and improve content delivery efficiency.

HTTP/2 is configured per CDN Resource in the [Medianova Control Panel](https://cloud.medianova.com).

## Configure HTTP/2

{% stepper %}
{% step %}

### Open Protocols

Open your CDN Resource and navigate to **Optimization → Protocols**.
{% endstep %}

{% step %}

### Enable HTTP/2

Enable the **HTTP/2** toggle.

Clients that support HTTP/2 can use the protocol for their connections to the CDN.
{% endstep %}

{% step %}

### Save the Configuration

Select **Save** in the pending changes bar.

Review the pending configuration changes and confirm the update.
{% endstep %}
{% endstepper %}

## HTTP/2 Behavior

When HTTP/2 is enabled:

* Supported clients can use HTTP/2 for communication with the CDN.
* Multiple requests and responses can be transferred over a single connection.
* Clients that do not support HTTP/2 automatically fall back to an earlier supported HTTP version.
* The setting applies to **client-to-CDN communication only**.
* Origin communication behavior is not modified by this setting.

### Important Notes

* HTTP/2 protocol negotiation occurs between the client and the CDN.
* No application-side changes are required to use HTTP/2 when the client supports it.
* Configuration changes are not applied until the pending changes are saved.


---

# 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/static-content-delivery/advanced-configuration/http-2.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.