Chapter 4. Transition to HTTP/2
To be flip and mildly unhelpful, one could say that in order to support HTTP/2 all you need to do is upgrade to a web server that speaks h2, or use a Content Delivery Network (CDN) that will front your website and speak it for you. Though true, it is glossing over a host of subtleties that may not be obvious and could result in unexpected higher costs or suboptimal performance. Here are a handful of the items you should consider before turning HTTP/2 on for your website:
-
Browser support for h2
-
Potential move to serving over TLS (HTTPS)
-
Tuning your website for h2 (possibly untuning for h1)
-
Third parties on your site
-
Retaining support for old clients
This chapter explains what you need to know about each of these topics.
Browser Support
As of publishing time, around 80% of web browsers in use support h2 to some degree.1 This means a significant portion of people will start reaping the benefits of h2 as soon as it is turned on. Since the protocol negotiation is transparent to non-h2 supporting browsers, anyone who does not speak h2 will simply fall back to h1 and still access your infrastructure. (You did keep h1 support for now, right?)
Table 4-1 lists browsers and the latest version supporting HTTP/2.
| Name | Since version | Notes |
|---|---|---|
Chrome |
41 |
|
Firefox |
36 |
|
Edge |
12 |
|
Safari |
9 |
OSX 10.11 and later |
Internet Explorer |
11 |
Windows 10 only |
Opera |
28 |
|
Safari - iOS |
9.2 |
|
Android Browser |
51 |
|
Chrome - ... |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access