We incorporate HTTP/2 support via CloudFlare

Starting today, HTTP/2 support is available to all Duplika customers for free and as part of the CloudFlare community.

An update that made itself desired

HTTP/2 is the first update to the Hypertext Transfer Protocol (HTTP) since 1999, with the aim of improving the performance of websites for the user who visits them from their preferred browser (end-user).

In November 2009, after a decade had passed with no news on the protocol, Google introduced an experimental protocol called SPDY. Efforts focused, among other things, on reducing Internet latency.

That internal project ended up becoming the basis for the brilliant HTTP/2, which was complemented with contributions from the Internet community and ended up being made official as a Web Standard.

What are the benefits of HTTP/2

HTTP/2 generates benefits for three parties: the end user, network and server resources.

With the previous protocol, HTTP/1.1, the main drawback was that each request used its own TCP connection. For example, one to download an image, another to download a CSS library, another for each javascript, another for the html, and so on.

To fix it, there is now the multiplexing (Multiplexing), which allows the browser to include multiple requests on a single TCP connection.

So instead of loading one resource at a time, as was the case previously, with HTTP/2 the browser requests all the web assets (CSS style sheets, Javascript files, and images) together, greatly speeding up site load time.

In HTTP/2, multiplexing is enhanced by the flow prioritization (Stream Priority), a mechanism that allows the browser to determine which web assets it prefers to receive first.

Thus, to the possibility of sending several requests in a single TCP connection, HTTP/2 adds the option of defining the order in which the assets will arrive. For example, you can request the HTML page first, followed by the style sheet, Javascript and the images at the end, in order to be able to display the text content of the web page with priority, and discover all the content dynamically and in an orderly manner. as it is received.

Also with the goal of speeding up data transmission, HTTP/2 adds the header compression.

Which is a Headboard? Well, every time a browser requests a asset web, one is included HTTP header on request; a "manual" that explains how the data of its respective package should be treated. The browser, for example Chrome, must wait for the response from the server before it can send the next request. If you multiply the round trip for each asset included in an average web page, the amount of redundant information going back and forth translates into unnecessary delay.

The solution proposed by HTTP/2 is to send compressed headers, which force the amount of information exchanged between the client and the server to be considerably reduced.

How is HTTP/2 enabled?

If you're a Duplika user, then you don't have to make any changes to your website: support for HTTP/2 under TLS/SSL is already enabled.

Although the updated protocol does not require encrypted connections, the development teams of the most used browsers agreed that they will only support HTTP/2 over TLS connections. That is, in order to take advantage of HTTP/2, it must be possible to browse the sites under https (in other words, with SSL certificate).

Fortunately, if you do not have an SSL certificate installed on your hosting, Duplika offers you its Universal SSL via cloudflare.

All of our Duplika clients have the CloudFlare content accelerator integrated free of charge into their plans. Through this, the application of the newest and fastest internet protocol is ensured.

We are Duplika

Give your site the hosting it deserves

no comments on We incorporate HTTP/2 support via CloudFlare


If you have an active service, we recommend contacting us from our support platform.

I will be back soon

Hi 👋
Select the prefered contact method to get in touch.
Connect via: