We are excited to announce that on March 31, 2017, Verizon Digital Media Services will enable HTTP/2 delivery for all customers. The rollout of HTTP/2 will be gradual, and you may start to see some of your content being delivered over HTTP/2 before March 31. HTTP/2 is a major revision of the HTTP network protocol used to deliver traffic over the web. The focus of the protocol is on performance; specifically, user perceived latency, network and server resource usage. Enabling delivery of HTTP/2 offers increased performance without the need to update any of your code base. In fact, you shouldn’t need to change anything to start enjoying the benefits of HTTP/2.
Enabling HTTP/2 will impact all customers with SSL certificates deployed on the Verizon Digital Media Services content delivery network (CDN). If you are a customer with an SSL certificate deployed, you will not need to do anything. Customers with HTTP/2-enabled browsers will be able to communicate with our edge servers over HTTP/2 with no additional action required.
If you are a customer with an SSL certificate deployed, and you do not wish to have HTTP/2 enabled, please let your account manager or sales professional know, and we can disable the HTTP/2 protocol for your domains on your SSL certificate(s).
If there are any questions about these changes, please reach out to your account manager or sales professional.
Q: What does this mean for my website?
A: You will not need to change your website or application to use HTTP/2. Not only will your websites and applications continue to work as is, but they will also likely perform better and consume fewer resources on both the client and server.
Q: If I don’t have an SSL certificate, can I use HTTP/2?
A: No. An SSL certificate is required. This a restriction put in place by all major browsers, not Verizon Digital Media Services. If you would like to have an SSL certificate deployed so that you can enjoy the benefits of HTTP/2, please contact your account manager or sales professional.
Q: Is HTTP/2 enabled end to end?
A: HTTP/2 will only be enabled on the connection between the client and edge server. Any cache misses that require a connection to an origin server will be made over HTTP/1.1.
Q: Are you removing support for older versions of HTTP?
A: No. HTTP/2 will be added to a list of protocols used to communicate between a browser and the CDN. The CDN will continue to serve content over HTTP/1.1 or HTTP/1.0 to browsers that do not support HTTP/2 or for accounts that do not have HTTP/2 enabled.
Q: I have some questions. What should I do?
A: If there are any questions about these changes, please reach out to your account manager or sales professional.