> 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

**HTTP/2** improves content delivery performance by allowing multiple requests and responses to be multiplexed over a single connection. This reduces latency, minimizes connection overhead, and improves page load efficiency for supported clients.

You can manage HTTP/2 in the [Medianova Control Panel](https://cloud.medianova.com).

Navigate to the relevant CDN Resource and open the **Protocol Optimization** section.

### Configure HTTP/2

{% stepper %}
{% step %}

### Enable HTTP/2

<figure><img src="/files/RjxGevnK6iOBTaXjv0EO" alt=""><figcaption></figcaption></figure>

Toggle **HTTP/2** to **On.**
{% endstep %}
{% endstepper %}

### Behaviour

* HTTP/2 is used automatically when supported by the client.
* Multiple requests can be transferred over a single connection.
* Clients that do not support HTTP/2 automatically fall back to earlier HTTP versions.
* This setting affects client-to-CDN communication only.
* Origin communication behavior is not modified by this setting.

### Benefits

* Reduces connection overhead.
* Improves page load performance.
* Reduces latency for websites with many assets.
* Improves network efficiency through multiplexing.

### FAQ

**Do all browsers support HTTP/2?**\
Most modern browsers support HTTP/2. Unsupported clients automatically use an earlier HTTP version

**Does enabling HTTP/2 require application changes?**\
No. HTTP/2 is negotiated automatically between the client and the CDN.

**Does this setting affect communication with the origin server?**\
No. It only controls the protocol used between clients and the CDN edge.


---

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