Skip to content

HTTP/2 Support disclaimer update #8209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 7 commits into
base: develop
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion pages/network/load_balancer/case_http2/guide.de-de.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,29 @@
---
title: Konfiguration von HTTP/2 auf dem OVHcloud Loadbalancer
excerpt: So konfigurieren Sie HTTP/2 auf dem OVHcloud Loadbalancer
updated: 2025-07-04
updated: 2025-07-24
---

> [!primary]
> **Hinweis auf native HTTP/2-Medien**
>
> Seit Juni 2025 unterstützen die HTTP- und TLS-Frontends der OVHcloud Loadbalancer-Dienste nativ das HTTP/2-Protokoll.
>
> Für TCP-Frontends, die für Anwendungen mit geringer Latenz und hoher Leistung nützlich sein können, gilt jedoch die folgende Anleitung.
>
> HTTP/2 verbessert die Performance Ihrer Web-Applikationen durch:
>
> - *Schnellere Ladezeiten* durch Query Multiplexing, das es ermöglicht, mehrere Anfragen parallel über eine Verbindung zu senden.
> - *Reduzierte Latenz* mit besserem Verbindungsmanagement.
> - *Optimierung der Netzwerkressourcen* durch Header-Komprimierung.
>
> Um das HTTP/2-Protokoll auf bestehenden HTTP- und TLS-Frontends zu aktivieren, führen Sie den unten stehenden Aufruf zum Aktualisieren über die API aus, wobei **serviceName** der interne Name Ihres Loadbalancers ist.

> [!api]
>
> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh
>

## Einleitung

Das HTTP/2-Protokoll wird aktuell nicht vom OVHcloud Loadbalancer unterstützt. Sie können diese Einschränkung jedoch umgehen, indem Sie den TCP-Modus mit der ALPN-Erweiterung des TLS-Protokolls verwenden.
Expand Down
36 changes: 25 additions & 11 deletions pages/network/load_balancer/case_http2/guide.en-asia.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,38 @@
---
title: Configuring HTTP/2 on an OVHcloud Load Balancer service
excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service
updated: 2025-07-04
title: Configuring HTTP/2 on an OVH Load Balancer service
excerpt: Configuring HTTP/2 on an OVH Load Balancer service
updated: 2025-07-24
---

> [!primary]
> **Notice on HTTP/2 native support**
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends, which may be useful in high performance, low latency applications.
>
> HTTP/2 brings numerous advantages to enhance the performance and efficiency of your applications:
>
> - *Faster load times* thanks to multiplexing, which allows multiple requests to be sent in parallel on the same connection.
> - *Reduced latency* by limiting the exchanges between the client and the server.
> - *Optimized network performance* through header compression.
>
> In order to enable HTTP/2 on existing HTTP and TLS frontends, you must make the following refresh call via the API, where **{serviceName}** is the internal name of your Load Balancer.
>

> [!api]
>
> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh
>

## Objective

The OVHcloud Load Balancer does not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.
The OVHcloud Load Balancer TCP frontends do not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.

ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables the application layer to negotiate which protocol will be used (h2 in this case).

**This guide is designed to help you create an HTTP/2 service with the OVHcloud Load Balancer solution. Here, we will configure this service to balance the load across several servers responding with HTTP/2.**

> [!primary]
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends.
>

## Requirements

- You need to have created a TCP front-end.
Expand Down
36 changes: 25 additions & 11 deletions pages/network/load_balancer/case_http2/guide.en-au.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,38 @@
---
title: Configuring HTTP/2 on an OVHcloud Load Balancer service
excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service
updated: 2025-07-04
title: Configuring HTTP/2 on an OVH Load Balancer service
excerpt: Configuring HTTP/2 on an OVH Load Balancer service
updated: 2025-07-24
---

> [!primary]
> **Notice on HTTP/2 native support**
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends, which may be useful in high performance, low latency applications.
>
> HTTP/2 brings numerous advantages to enhance the performance and efficiency of your applications:
>
> - *Faster load times* thanks to multiplexing, which allows multiple requests to be sent in parallel on the same connection.
> - *Reduced latency* by limiting the exchanges between the client and the server.
> - *Optimized network performance* through header compression.
>
> In order to enable HTTP/2 on existing HTTP and TLS frontends, you must make the following refresh call via the API, where **{serviceName}** is the internal name of your Load Balancer.
>

> [!api]
>
> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh
>

## Objective

The OVHcloud Load Balancer does not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.
The OVHcloud Load Balancer TCP frontends do not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.

ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables the application layer to negotiate which protocol will be used (h2 in this case).

**This guide is designed to help you create an HTTP/2 service with the OVHcloud Load Balancer solution. Here, we will configure this service to balance the load across several servers responding with HTTP/2.**

> [!primary]
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends.
>

## Requirements

- You need to have created a TCP front-end.
Expand Down
36 changes: 25 additions & 11 deletions pages/network/load_balancer/case_http2/guide.en-ca.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,38 @@
---
title: Configuring HTTP/2 on an OVHcloud Load Balancer service
excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service
updated: 2025-07-04
title: Configuring HTTP/2 on an OVH Load Balancer service
excerpt: Configuring HTTP/2 on an OVH Load Balancer service
updated: 2025-07-24
---

> [!primary]
> **Notice on HTTP/2 native support**
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends, which may be useful in high performance, low latency applications.
>
> HTTP/2 brings numerous advantages to enhance the performance and efficiency of your applications:
>
> - *Faster load times* thanks to multiplexing, which allows multiple requests to be sent in parallel on the same connection.
> - *Reduced latency* by limiting the exchanges between the client and the server.
> - *Optimized network performance* through header compression.
>
> In order to enable HTTP/2 on existing HTTP and TLS frontends, you must make the following refresh call via the API, where **{serviceName}** is the internal name of your Load Balancer.
>

> [!api]
>
> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh
>

## Objective

The OVHcloud Load Balancer does not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.
The OVHcloud Load Balancer TCP frontends do not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.

ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables the application layer to negotiate which protocol will be used (h2 in this case).

**This guide is designed to help you create an HTTP/2 service with the OVHcloud Load Balancer solution. Here, we will configure this service to balance the load across several servers responding with HTTP/2.**

> [!primary]
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends.
>

## Requirements

- You need to have created a TCP front-end.
Expand Down
75 changes: 60 additions & 15 deletions pages/network/load_balancer/case_http2/guide.en-gb.md
Original file line number Diff line number Diff line change
@@ -1,30 +1,73 @@
---
title: Configuring HTTP/2 on an OVH Load Balancer service
excerpt: Configuring HTTP/2 on an OVH Load Balancer service
updated: 2025-07-04
excerpt: Choose and configure the frontends of your OVHcloud Load Balancer service, for usage with the HTTP/2 protocol
updated: 2025-07-30
---

## Objective

The OVH Load Balancer does not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.

ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables the application layer to negotiate which protocol will be used (h2 in this case).

**This guide is designed to help you create an HTTP/2 service with the OVH Load Balancer solution. Here, we will configure this service to balance the load across several servers responding with HTTP/2.**

> [!primary]
> **Notice on HTTP/2 native support**
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends.
> However, the following guide remains applicable for TCP frontends, which may be useful in high performance, low latency applications.
>
> In order to enable HTTP/2 on existing HTTP and TLS frontends, you must make the following refresh call via the API, where **{serviceName}** is the internal name of your Load Balancer.
>

> [!api]
>
> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh
>

## Objective

This guide serves two primary purposes:
- To help you understand the distinctions between TCP, HTTP, and TLS frontends on an OVHcloud Load Balancer, enabling you to determine if a TCP frontend is the most suitable choice for your specific application requirements, especially when dealing with HTTP/2 traffic.
- If a TCP frontend is deemed desirable, to then provide step-by-step instructions on how to configure it to effectively balance HTTP/2 traffic across your backend servers.


## Requirements

- You need to have created a TCP front-end.
- You need to have created a TCP farm, with servers added to it.
You will need:
- An OVHcloud Load Balancer service;
- A TCP frontend on your Load Balancer;
- A TCP backend cluster with at least one server added to it;
- Backend servers configured to support and respond with HTTP/2.

## Instructions
## Why use HTTP/2 ?

HTTP/2 brings numerous advantages to enhance the performance and efficiency of your applications:

- *Faster load times* thanks to multiplexing, which allows multiple requests to be sent in parallel on the same connection.
- *Reduced latency* by limiting the exchanges between the client and the server.
- *Optimized network performance* through header compression.

## Differences between HTTP/2 and TCP frontends

A TCP frontend operates at Layer 4 (the transport layer) of the OSI model. When you configure a TCP frontend, the load balancer establishes a TCP connection between the client and a backend server. This means the load balancer doesn't inspect or understand the HTTP/2 data within the TCP stream. Consequently, TCP frontends offer high performance due to minimal processing needs.

However, because it doesn't understand the application protocol, it cannot perform advanced HTTP-specific optimizations, like content-based routing or HTTP header manipulation.

HTTP and TLS frontends, conversely, operate at Layer 7 (the application layer). When a client connects to an HTTP/2-compatible frontend, the load balancer fully decodes the HTTP/2 frames before establishing a connection with a backend server.

By understanding the application protocol, an HTTP/2-compatible frontend can provide numerous advanced features. These include SSL/TLS termination (offloading encryption/decryption from backend servers), content-based routing (e.g., routing requests to different backend pools based on URL path or headers), request/response modification, and HTTP/2 multiplexing.

**You should use a TCP frontend when:**
- You need to load balance other non-HTTP services (e.g., databases, custom TCP applications, SSH);
- You require maximum performance and minimal latency;
- Your backend servers are already handling SSL/TLS termination;
- You don't need advanced HTTP-specific features like content-based routing, HTTP header manipulation, or HTTP/2 protocol-level optimizations.

**You should use an HTTP/2-compatible frontend when:**
- You are primarily load balancing web traffic (HTTP/HTTPS);
- You want to leverage the performance benefits of HTTP/2 between the client and the load balancer;
- You need to offload SSL/TLS termination from your backend servers;
- You require advanced routing logic based on HTTP headers, URLs, or other application-layer attributes;
- You want to optimize the client-side experience by taking advantage of HTTP/2 features.

*If you choose to use a TCP frontend, follow the next steps of this guide to configure it for HTTP/2 usage*.

## Configure a TCP frontend for use with HTTP/2

> [!warning]
>
Expand Down Expand Up @@ -140,7 +183,7 @@ Refresh a zone:

### Confirm

After you have completed all of these steps, you should have a functional load balancer service for your HTTP/2 servers. You can now confirm the status of your service by requesting it from your OVH Load Balancer service, then verifying the response version:
After you have completed these steps, you should have a functional load balancer service for your HTTP/2 servers. You can now confirm the status of your service by requesting it from your OVH Load Balancer service, then verifying the response version:

```bash
curl -I --http2 https://www.ovh.co.uk/
Expand All @@ -149,4 +192,6 @@ HTTP/2 200

## Go further

If you want more information about the HTTP/2 protocol, please visit <https://http2.github.io/>.

Join our community of users on <https://community.ovh.com/en/>.
36 changes: 25 additions & 11 deletions pages/network/load_balancer/case_http2/guide.en-sg.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,38 @@
---
title: Configuring HTTP/2 on an OVHcloud Load Balancer service
excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service
updated: 2025-07-04
title: Configuring HTTP/2 on an OVH Load Balancer service
excerpt: Configuring HTTP/2 on an OVH Load Balancer service
updated: 2025-07-24
---

> [!primary]
> **Notice on HTTP/2 native support**
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends, which may be useful in high performance, low latency applications.
>
> HTTP/2 brings numerous advantages to enhance the performance and efficiency of your applications:
>
> - *Faster load times* thanks to multiplexing, which allows multiple requests to be sent in parallel on the same connection.
> - *Reduced latency* by limiting the exchanges between the client and the server.
> - *Optimized network performance* through header compression.
>
> In order to enable HTTP/2 on existing HTTP and TLS frontends, you must make the following refresh call via the API, where **{serviceName}** is the internal name of your Load Balancer.
>

> [!api]
>
> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh
>

## Objective

The OVHcloud Load Balancer does not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.
The OVHcloud Load Balancer TCP frontends do not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.

ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables the application layer to negotiate which protocol will be used (h2 in this case).

**This guide is designed to help you create an HTTP/2 service with the OVHcloud Load Balancer solution. Here, we will configure this service to balance the load across several servers responding with HTTP/2.**

> [!primary]
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends.
>

## Requirements

- You need to have created a TCP front-end.
Expand Down
36 changes: 25 additions & 11 deletions pages/network/load_balancer/case_http2/guide.en-us.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,38 @@
---
title: Configuring HTTP/2 on an OVHcloud Load Balancer service
excerpt: Configuring HTTP/2 on an OVHcloud Load Balancer service
updated: 2025-07-04
title: Configuring HTTP/2 on an OVH Load Balancer service
excerpt: Configuring HTTP/2 on an OVH Load Balancer service
updated: 2025-07-24
---

> [!primary]
> **Notice on HTTP/2 native support**
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends, which may be useful in high performance, low latency applications.
>
> HTTP/2 brings numerous advantages to enhance the performance and efficiency of your applications:
>
> - *Faster load times* thanks to multiplexing, which allows multiple requests to be sent in parallel on the same connection.
> - *Reduced latency* by limiting the exchanges between the client and the server.
> - *Optimized network performance* through header compression.
>
> In order to enable HTTP/2 on existing HTTP and TLS frontends, you must make the following refresh call via the API, where **{serviceName}** is the internal name of your Load Balancer.
>

> [!api]
>
> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh
>

## Objective

The OVHcloud Load Balancer does not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.
The OVHcloud Load Balancer TCP frontends do not currently support the HTTP/2 protocol. However, you can bypass this restriction by using TCP mode with the ALPN extension of the TLS protocol.

ALPN (Application-Layer Protocol Negotiation) is a TLS extension that enables the application layer to negotiate which protocol will be used (h2 in this case).

**This guide is designed to help you create an HTTP/2 service with the OVHcloud Load Balancer solution. Here, we will configure this service to balance the load across several servers responding with HTTP/2.**

> [!primary]
>
> Since June 2025, HTTP and TLS frontends used by OVHcloud Load Balancer services natively support the HTTP/2 protocol.
>
> However, the following guide remains applicable for TCP frontends.
>

## Requirements

- You need to have created a TCP front-end.
Expand Down
Loading