diff --git a/pages/network/load_balancer/case_http2/guide.de-de.md b/pages/network/load_balancer/case_http2/guide.de-de.md index fc363c0029a..0fda8f3b198 100644 --- a/pages/network/load_balancer/case_http2/guide.de-de.md +++ b/pages/network/load_balancer/case_http2/guide.de-de.md @@ -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. diff --git a/pages/network/load_balancer/case_http2/guide.en-asia.md b/pages/network/load_balancer/case_http2/guide.en-asia.md index 3ceee968446..250d1e958f6 100644 --- a/pages/network/load_balancer/case_http2/guide.en-asia.md +++ b/pages/network/load_balancer/case_http2/guide.en-asia.md @@ -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. diff --git a/pages/network/load_balancer/case_http2/guide.en-au.md b/pages/network/load_balancer/case_http2/guide.en-au.md index 3ceee968446..250d1e958f6 100644 --- a/pages/network/load_balancer/case_http2/guide.en-au.md +++ b/pages/network/load_balancer/case_http2/guide.en-au.md @@ -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. diff --git a/pages/network/load_balancer/case_http2/guide.en-ca.md b/pages/network/load_balancer/case_http2/guide.en-ca.md index 3ceee968446..250d1e958f6 100644 --- a/pages/network/load_balancer/case_http2/guide.en-ca.md +++ b/pages/network/load_balancer/case_http2/guide.en-ca.md @@ -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. diff --git a/pages/network/load_balancer/case_http2/guide.en-gb.md b/pages/network/load_balancer/case_http2/guide.en-gb.md index 3dff4310cd6..86cb7d67af8 100644 --- a/pages/network/load_balancer/case_http2/guide.en-gb.md +++ b/pages/network/load_balancer/case_http2/guide.en-gb.md @@ -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] > @@ -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/ @@ -149,4 +192,6 @@ HTTP/2 200 ## Go further +If you want more information about the HTTP/2 protocol, please visit . + Join our community of users on . \ No newline at end of file diff --git a/pages/network/load_balancer/case_http2/guide.en-sg.md b/pages/network/load_balancer/case_http2/guide.en-sg.md index 3ceee968446..250d1e958f6 100644 --- a/pages/network/load_balancer/case_http2/guide.en-sg.md +++ b/pages/network/load_balancer/case_http2/guide.en-sg.md @@ -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. diff --git a/pages/network/load_balancer/case_http2/guide.en-us.md b/pages/network/load_balancer/case_http2/guide.en-us.md index 3ceee968446..250d1e958f6 100644 --- a/pages/network/load_balancer/case_http2/guide.en-us.md +++ b/pages/network/load_balancer/case_http2/guide.en-us.md @@ -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. diff --git a/pages/network/load_balancer/case_http2/guide.es-es.md b/pages/network/load_balancer/case_http2/guide.es-es.md index 8a5d7a5ba97..560eac4da0b 100644 --- a/pages/network/load_balancer/case_http2/guide.es-es.md +++ b/pages/network/load_balancer/case_http2/guide.es-es.md @@ -1,9 +1,29 @@ --- title: Configurar HTTP/2 en un Load Balancer de OVHcloud excerpt: Cómo configurar el protocolo HTTP/2 en un Load Balancer de OVHvloud -updated: 2025-07-04 +updated: 2025-07-24 --- +> [!primary] +> **Nota sobre el soporte nativo del protocolo HTTP/2** +> +> Desde junio de 2025, los frontends HTTP y TLS de los servicios Load Balancer de OVHcloud soportan de forma nativa el protocolo HTTP/2. +> +> Sin embargo, la siguiente guía sigue siendo aplicable para los frontends TCP, que pueden ser útiles para aplicaciones que requieren una baja latencia y un alto rendimiento. +> +> HTTP/2 mejora el rendimiento de sus aplicaciones web permitiendo: +> +> - *Tiempos de carga más rápidos* gracias al multiplexado de las peticiones, que permite enviar varias peticiones en paralelo en una misma conexión. +> - *Una reducción de la latencia* con una mejor gestión de las conexiones. +> - *Optimización de los recursos de red* gracias a la compresión de los encabezados. +> +> Para activar el protocolo HTTP/2 en los frontends HTTP y TLS existentes, debe realizar la siguiente llamada de actualización a través de la API, donde **serviceName** es el nombre interno del Load Balancer. + +> [!api] +> +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh +> + ## Objetivo Actualmente el Load Balancer de OVHcloud no soporta el protocolo HTTP/2, pero hay una forma de saltarse esta restricción: utilizar conjuntamente el modo TCP y la extensión ALPN del protocolo TLS. diff --git a/pages/network/load_balancer/case_http2/guide.es-us.md b/pages/network/load_balancer/case_http2/guide.es-us.md index 9b1c30d5682..ec08039e66b 100644 --- a/pages/network/load_balancer/case_http2/guide.es-us.md +++ b/pages/network/load_balancer/case_http2/guide.es-us.md @@ -1,9 +1,29 @@ --- title: Configurar HTTP/2 en un Load Balancer de OVHcloud excerpt: Cómo configurar el protocolo HTTP/2 en un Load Balancer de OVHcloud -updated: 2025-07-04 +updated: 2025-07-24 --- +> [!primary] +> **Nota sobre el soporte nativo del protocolo HTTP/2** +> +> Desde junio de 2025, los frontends HTTP y TLS de los servicios Load Balancer de OVHcloud soportan de forma nativa el protocolo HTTP/2. +> +> Sin embargo, la siguiente guía sigue siendo aplicable para los frontends TCP, que pueden ser útiles para aplicaciones que requieren una baja latencia y un alto rendimiento. +> +> HTTP/2 mejora el rendimiento de sus aplicaciones web permitiendo: +> +> - *Tiempos de carga más rápidos* gracias al multiplexado de las peticiones, que permite enviar varias peticiones en paralelo en una misma conexión. +> - *Una reducción de la latencia* con una mejor gestión de las conexiones. +> - *Optimización de los recursos de red* gracias a la compresión de los encabezados. +> +> Para activar el protocolo HTTP/2 en los frontends HTTP y TLS existentes, debe realizar la siguiente llamada de actualización a través de la API, donde **serviceName** es el nombre interno del Load Balancer. + +> [!api] +> +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh +> + ## Objetivo Actualmente el Load Balancer de OVHcloud no soporta el protocolo HTTP/2, pero hay una forma de saltarse esta restricción: utilizar conjuntamente el modo TCP y la extensión ALPN del protocolo TLS. diff --git a/pages/network/load_balancer/case_http2/guide.fr-ca.md b/pages/network/load_balancer/case_http2/guide.fr-ca.md index 3203d5e1bc4..e79614310a0 100644 --- a/pages/network/load_balancer/case_http2/guide.fr-ca.md +++ b/pages/network/load_balancer/case_http2/guide.fr-ca.md @@ -1,9 +1,29 @@ --- title: 'Configurer HTTP/2 sur un service OVHcloud Load Balancer' excerpt: 'Configuration de HTTP/2 sur un service OVHcloud Load Balancer' -updated: 2025-07-04 +updated: 2025-07-24 --- +> [!primary] +> **Note sur le support natif du protocole HTTP/2** +> +> Depuis juin 2025, les frontends HTTP et TLS des services Load Balancer OVHcloud supportent nativement le protocole HTTP/2. +> +> Le guide suivant reste cependant applicable pour les frontends TCP, qui peuvent être utiles pour des applications nécessitant une faible latence et de hautes performances. +> +> HTTP/2 améliore les performances de vos applications web en permettant : +> +> - *Des temps de chargement plus rapides* grâce au multiplexage des requêtes, qui permet d'envoyer plusieurs requêtes en parallèle sur une même connexion. +> - *Une réduction de la latence* avec une meilleure gestion des connexions. +> - *Une optimisation des ressources réseau* grâce à la compression des en-têtes. +> +> Afin d'activer le protocole HTTP/2 sur des frontends HTTP et TLS existants, vous devez effectuer l'appel de rafraîchissement ci-dessous via l'API, où **serviceName** est le nom interne de votre Load Balancer. + +> [!api] +> +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh +> + ## Objectif L'OVHcloud Load Balancer ne supporte pas actuellement le protocole HTTP/2. Il existe cependant un moyen de contourner cette restriction, en utilisant conjointement le mode TCP et l'extension ALPN du protocole TLS. diff --git a/pages/network/load_balancer/case_http2/guide.fr-fr.md b/pages/network/load_balancer/case_http2/guide.fr-fr.md index 0619354ff08..be360ba8458 100644 --- a/pages/network/load_balancer/case_http2/guide.fr-fr.md +++ b/pages/network/load_balancer/case_http2/guide.fr-fr.md @@ -1,32 +1,74 @@ --- title: 'Configurer HTTP/2 sur un service OVHcloud Load Balancer' excerpt: 'Configuration de HTTP/2 sur un service OVHcloud Load Balancer' -updated: 2025-07-04 +updated: 2025-07-24 --- -## Objectif - -L'OVHcloud Load Balancer ne supporte pas le protocole HTTP/2. Il existe cependant un moyen de contourner cette restriction, en utilisant conjointement le mode TCP et l'extension ALPN du protocole TLS. - -ALPN (Application-Layer Protocol Negotiation) est une extension TLS qui permet à la couche applicative de négocier quel protocole sera utilisé (h2 dans notre cas). - -**Ce guide a pour but de vous aider à créer un service HTTP/2 avec l'offre Load Balancer OVHcloud. Nous allons ici configurer ce service pour répartir la charge sur plusieurs serveurs répondant en HTTP/2.** - > [!primary] +> **Note sur le support natif du protocole HTTP/2** +> +> Depuis juin 2025, les frontends HTTP et TLS des services Load Balancer OVHcloud supportent nativement le protocole HTTP/2. +> +> Le guide suivant reste cependant applicable pour les frontends TCP, qui peuvent être utiles pour des applications nécessitant une faible latence et de hautes performances. > -> Depuis juin 2025, les frontend HTTP et TLS des services Load Balancer OVHcloud supportent nativement le protocole HTTP/2. +> Afin d'activer le protocole HTTP/2 sur des frontends HTTP et TLS existants, vous devez effectuer l'appel de rafraîchissement ci-dessous via l'API, où **serviceName** est le nom interne de votre Load Balancer. + +> [!api] > -> Le guide suivant reste cependant applicable pour les frontend TCP. +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > +## Objectif + +Ce guide a deux objectifs principaux : + +- Vous aider à comprendre les distinctions entre les frontends TCP, HTTP et TLS sur un Load Balancer OVHcloud, vous permettant ainsi de déterminer si un frontend TCP est le choix le plus approprié pour vos besoins applicatifs spécifiques, en particulier lors de la gestion du trafic HTTP/2. +- Si un frontend TCP est jugé souhaitable, fournir ensuite des instructions étape par étape sur la façon de le configurer pour équilibrer efficacement le trafic HTTP/2 sur vos serveurs backend. + ## Prérequis -- Disposer d'un [Load Balancer OVHcloud](/links/network/load-balancer){.external} (Pack 2 minimum). -- Un frontend TCP créé sur le port 443. -- Une ferme TCP créée et des serveurs ajoutés. -- Avoir accès à l'[API OVHcloud](/links/api){.external}. -## En pratique +Vous aurez besoin de : + +- Un service Load Balancer OVHcloud ; +- Un frontend TCP sur votre Load Balancer ; +- Un cluster de serveurs (ferme) TCP avec au moins un serveur ajouté ; +- Des serveurs backend configurés pour prendre en charge et répondre avec HTTP/2. + +## Pourquoi utiliser HTTP/2 ? + +HTTP/2 apporte de nombreux avantages pour améliorer les performances et l'efficacité de vos applications : + +- *Temps de chargement plus rapides* grâce au multiplexage, qui permet d'envoyer plusieurs requêtes en parallèle sur la même connexion. +- *Latence réduite* en limitant les échanges entre le client et le serveur. +- *Performances réseau optimisées* grâce à la compression des en-têtes. + +## Différences entre les frontends HTTP/2 et TCP + +Un frontend TCP opère à la Couche 4 (la couche de transport) du modèle OSI. Lorsque vous configurez un frontend TCP, le Load Balancer établit une connexion TCP entre le client et un serveur backend. Cela signifie que le Load Balancer n'inspecte ni ne comprend les données HTTP/2 au sein du flux TCP. Par conséquent, les frontends TCP offrent des performances élevées grâce à un traitement minimal des données. + +Cependant, comme il ne comprend pas le protocole applicatif, il ne peut pas effectuer d'optimisations avancées spécifiques à HTTP, telles que le routage basé sur le contenu ou la manipulation des en-têtes HTTP. + +Les frontends HTTP et TLS, quant à eux, opèrent à la Couche 7 (la couche application). Lorsqu'un client se connecte à un frontend compatible HTTP/2, le Load Balancer décode entièrement les trames HTTP/2 avant d'établir une connexion avec un serveur backend. + +En interprétant le protocole applicatif, un frontend compatible HTTP/2 peut fournir de nombreuses fonctionnalités avancées. Celles-ci incluent la terminaison SSL/TLS (déchargeant le chiffrement/déchiffrement des serveurs backend), le routage basé sur le contenu (par exemple, le routage des requêtes vers différentes fermes de backend en fonction du chemin d'URL ou des en-têtes), la modification des requêtes/réponses et le multiplexage HTTP/2. + +**Vous devriez utiliser un frontend TCP lorsque :** +- Vous devez équilibrer la charge d'autres services non-HTTP (par exemple, des bases de données, des applications TCP personnalisées, SSH) ; +- Vous exigez des performances maximales et une latence minimale ; +- Vos serveurs backend gèrent déjà la terminaison SSL/TLS ; +- Vous n'avez pas besoin de fonctionnalités HTTP avancées spécifiques telles que le routage basé sur le contenu, la manipulation des en-têtes HTTP ou les optimisations au niveau du protocole HTTP/2. + +**Vous devriez utiliser un frontend compatible HTTP/2 lorsque :** +- Vous traitez principalement du trafic web (HTTP/HTTPS) ; +- Vous souhaitez tirer parti des avantages de performance de HTTP/2 entre le client et le Load Balancer ; +- Vous souhaitez déléguer la terminaison SSL/TLS de vos serveurs backend à votre Load Balancer ; +- Vous avez besoin d'une logique de routage avancée basée sur les en-têtes HTTP, les URL ou d'autres attributs de la couche application ; +- Vous souhaitez optimiser l'expérience côté client en tirant parti des fonctionnalités HTTP/2. + +*Si vous choisissez d'utiliser un frontend TCP, suivez les étapes suivantes de ce guide pour le configurer pour une utilisation HTTP/2*. + +## Configurer un frontend TCP pour HTTP/2 > [!warning] > diff --git a/pages/network/load_balancer/case_http2/guide.it-it.md b/pages/network/load_balancer/case_http2/guide.it-it.md index b43261c47a2..ea23eb9afc7 100644 --- a/pages/network/load_balancer/case_http2/guide.it-it.md +++ b/pages/network/load_balancer/case_http2/guide.it-it.md @@ -1,9 +1,29 @@ --- title: 'Configurare HTTP/2 su OVHcloud Load Balancer' excerpt: 'Configurazione di HTTP/2 su OVHcloud Load Balancer' -updated: 2025-07-04 +updated: 2025-07-24 --- +> [!primary] +> **Nota sul supporto nativo del protocollo HTTP/2** +> +> Da giugno 2025, i frontend HTTP e TLS dei servizi Load Balancer OVHcloud supportano nativamente il protocollo HTTP/2. +> +> Questa guida è valida per i frontend TCP, che possono essere utili per applicazioni che richiedono latenza ridotta e prestazioni elevate. +> +> HTTP/2 migliora le performance delle tue applicazioni Web permettendo: +> +> - *Tempi di caricamento più rapidi* grazie alla moltiplicazione delle richieste, che permette di inviare più richieste in parallelo sulla stessa connessione. +> - *Riduzione della latenza* con una migliore gestione delle connessioni. +> - *Ottimizzazione delle risorse di rete* grazie alla compressione delle intestazioni. +> +> Per attivare il protocollo HTTP/2 sui frontend HTTP e TLS esistenti, effettua la chiamata di aggiornamento qui sotto via API, dove **serviceName** è il nome interno del Load Balancer. + +> [!api] +> +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh +> + ## Obiettivo Attualmente, OVHcloud Load Balancer non supporta il protocollo HTTP/2, ma esiste un modo per aggirare questo limite utilizzando contemporaneamente la modalità TCP e l'estensione ALPN del protocollo TLS. diff --git a/pages/network/load_balancer/case_http2/guide.pl-pl.md b/pages/network/load_balancer/case_http2/guide.pl-pl.md index 9544e335e8c..253bae8ef07 100644 --- a/pages/network/load_balancer/case_http2/guide.pl-pl.md +++ b/pages/network/load_balancer/case_http2/guide.pl-pl.md @@ -1,9 +1,29 @@ --- title: Konfiguracja HTTP/2 w usłudze Load Balancer excerpt: Dowiedz się, jak skonfigurować HTTP/2 w usłudze Load Balancer -updated: 2025-07-04 +updated: 2025-07-24 --- +> [!primary] +> **Notatka dotycząca macierzystej obsługi protokołu HTTP/2** +> +> Od czerwca 2025 front-endy HTTP i TLS usług Load Balancer OVHcloud wspierają natywnie protokół HTTP/2. +> +> Poniższy przewodnik ma jednak zastosowanie do front-endów TCP, które mogą być przydatne w przypadku aplikacji wymagających niewielkich opóźnień i wysokiej wydajności. +> +> HTTP/2 zwiększa wydajność aplikacji www pozwalając na: +> +> - *Krótsze czasy ładowania* dzięki multipleksowaniu zapytań, które pozwala na wysyłanie wielu zapytań jednocześnie do tego samego połączenia. +> - *Krótszy czas odpowiedzi* z lepszą obsługą połączeń. +> - *Optymalizacja zasobów sieciowych* poprzez kompresję nagłówków. +> +> Aby włączyć protokół HTTP/2 dla istniejących front-endów HTTP i TLS, należy wykonać poniższe wywołanie odświeżania przez API, gdzie **serviceName** jest wewnętrzną nazwą Twojego Load Balancera. + +> [!api] +> +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh +> + ## Wprowadzenie Obecnie Load Balancer nie wspiera protokołu HTTP/2. Istnieje jednak możliwość ominięcia tego ograniczenia dzięki łącznemu użyciu trybu TCP i rozszerzenia ALPN protokołu TLS. diff --git a/pages/network/load_balancer/case_http2/guide.pt-pt.md b/pages/network/load_balancer/case_http2/guide.pt-pt.md index 8fcbeb7fb77..f721c6940fb 100644 --- a/pages/network/load_balancer/case_http2/guide.pt-pt.md +++ b/pages/network/load_balancer/case_http2/guide.pt-pt.md @@ -1,9 +1,29 @@ --- title: 'Como configurar o protocolo HTTP/2 no Load Balancer OVHcloud' excerpt: 'Configuração do protocolo HTTP/2 no Load Balancer OVHcloud' -updated: 2025-07-04 +updated: 2025-07-24 --- +> [!primary] +> **Nota sobre o suporte nativo do protocolo HTTP/2** +> +> Desde junho de 2025, os Frontends HTTP e TLS dos serviços Load Balancer da OVHcloud suportam nativamente o protocolo HTTP/2. +> +> O seguinte manual continua a ser aplicável aos Frontends TCP, que podem ser úteis para aplicações que exigem baixa latência e alto desempenho. +> +> HTTP/2 melhora as performances das suas aplicações web ao permitir: +> +> - *Tempos de carregamento mais rápidos* graças à multiplicação dos pedidos, que permite enviar vários pedidos em paralelo numa mesma ligação. +> - *Uma redução da latência* com uma melhor gestão das ligações. +> - *Otimização de recursos de rede* através da compressão de cabeçalhos. +> +> Para ativar o protocolo HTTP/2 em Frontends HTTP e TLS existentes, deve efetuar a chamada de atualização abaixo através da API, onde **serviceName** é o nome interno do seu Load Balancer. + +> [!api] +> +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh +> + ## Sumário Neste momento, o Load Balancer OVHcloud não é compatível com protocolo HTTP/2. No entanto,é possível contornar esta limitação usando o modo TCP com a extensão ALPN do protocolo TLS.