Chapter 3. Upgrading to HTTP/2

 

This chapter covers

  • HTTP/2 support in browsers and servers
  • Different options to enable HTTP/2 for your website
  • Reverse proxies and CDNs and how they affect HTTP/2
  • Troubleshooting why HTTP/2 isn’t being used

In the first two chapters, I introduced HTTP and showed where it fits on the web today; then I explained why HTTP/2 was a necessary upgrade that should be faster than HTTP/1 for most sites. Now it’s time to get HTTP/2 working on your site so that you can see how much it will benefit you.

3.1. HTTP/2 support

HTTP/2 was formally approved as an internet standard in May 2015, so it’s still a relatively recent technology. As with all new technologies, implementers must decide when is the right time to embrace. Implement too soon, and the technology will be considered to be bleeding-edge and risky to implement, as the technology is likely to change considerably and may even be dropped if it turns out to be unsuccessful. Additionally, the ability to use the technology will be hampered by other parties that don’t support it, meaning that there’s potentially little to gain from being one of the first movers. On the flip side, the first movers prove the technology and pave the way for it to go mainstream.

3.2. Ways to enable HTTP/2 for your website

3.3. Troubleshooting HTTP/2 setup

Summary

sitemap