Now Shipping HTTP/2 Support
May 20, 2016 | Justin Dorfman
You can now deliver content from our edge servers over HTTP/2.
Chrome and other popular browsers still support SPDY, but we have removed it completely in favor of HTTP/2. This means that you can have us deliver your content over either HTTP/1.1 or HTTP/2. To enable HTTP/2, just follow the steps in this tutorial.
Below we answer some questions we’re anticipating about this release, but if you have any other questions, definitely start a live chat.
What happens if I had SPDY enabled on a zone?
It has automatically been converted to HTTP/2.
Are you using NPN or ALPN TLS extensions?
We compile our servers using OpenSSL 1.0.2 that supports both ALPN and NPN. Since browsers are starting to drop support for NPN (such as Chrome), ALPN will be used.
Will the API still work?
Yes. We are keeping the
spdy request/response parameter as well as adding
http2. Both will work the same.
Do you support server push?
No. At this time we only support the core features that make up the HTTP/2 connection: binary framing, multiplexing, header compression, etc.
Which browsers support HTTP/2?
Almost all major browsers support HTTP/2. You can find an updated list here.
Do I need an SSL certificate for HTTP/2 to work?
Yes. All major browsers require a secure connection for HTTP/2 to work. We have free and paid SSL options available.
Is HTTP/2 supported between your edge servers and my origin?
Connections from our edge servers to your origin are made over HTTP/1.x (1.1 if you have Origin Shield and 1.0 if you don’t). This is because HTTP/2 support is provided by a compiled module that acts on the inbound connections, not on connections Nginx initiates. (Nginx is the web server we use.)
The code that Nginx uses to initiate connections needs to be modified so that it can negotiate to different protocols on connections it makes outbound.
How can I check if my site is using HTTP/2 or not?