Configuring HTTP/2 on an OVHcloud Load Balancer service
Configuring HTTP/2 on an OVHcloud Load Balancer service
Configuring HTTP/2 on an OVHcloud Load Balancer service
Last updated 15th January 2018
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.
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.
The order in which you create elements is important: the routes must be configured before you attach them to rules.
We will add a route to our service.
serviceName
<Load Balancer ID>
action
type
"farm"
target
<ID of your TCP farm that must manage the HTTP/2>
frontendId
<ID of your front-end TCP 443>
We will now add a rule to our route.
serviceName
<Load Balancer ID>
routeId
<ID of the route created above>
field
"protocol"
match
"is"
pattern
"http/2.0"
The modifications made to your OVHcloud Load Balancer must be explicitly applied in each of the zones configured for your service. Only at this point will they be visible to your website visitors. This way, you can make complex configuration changes in one go.
If you have several zones, you must apply the same configuration for each of them.
Refresh a zone:
serviceName *
<Load Balancer ID>
zone
<zone to deploy the configuration in>
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 OVHcloud Load Balancer service, then verifying the response version:
curl -I --http2 https://www.ovh.com/ca/en/
HTTP/2 200
Join our community of users on https://community.ovh.com/en/.
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community