Everything You Need to Know About QUIC and HTTP3

The Internet waited decades for an upgrade to HTTP/1. But several features of HTTP/2 have proved problematic, and now just six years after its introduction, HTTP/3 has come on the scene along with a brand new transport protocol, QUIC.
In this video, we review the history of HTTP, explain how HTTP/3 fixes problems with HTTP/2 and introduces new challenges, and discuss the NGINX implementation of QUIC and HTTP/3.
NGINX and QUIC
quic.nginx.org/
Introducing a Technology Preview of NGINX Support for QUIC and HTTP/3
bit.ly/3OjKEUL
Chapters:
00:00 Introduction
00:14 Quick history breakdown of QUIC and HTTP3
04:03 HTTP/1.1 c. 1997
05:11 HTTP/2 c.2015
06:01 HTTP/3 .c2021
07:00 HTTP Stacks
07:43 HTTP Versions Today
09:26 Reality of HTTP Deployment
10:15 Environmental Factors
11:57 Revisiting the timeline of HTTP
12:29 What went wrong with HTTP/2
15:51 Head-of-line blocking hurts user experience
18:29 QUIC to the rescure
20:22 New Challenges
20:33 New Challenges: HTTP Version Negotiation
22:44 HTTP/3 Version Negotiation
23:52 New Challenges: UDP Exfiltration
25:00 nginx-quic
27:08 NGINX Configuration: HTTP/1
28:21 Summary of everything you need to know about QUIC and HTTP3

[@sonyarianto]

This is very good explanation of the evolving HTTP. This is gold content. I like concept explanation like this and will always useful anytime we watch it.

[@xorengames]

Great job on this presentation! Thanks for getting us up to speed on the current state of NGINX and the new features and challenges that HTTP3 will bring. I'm going to start testing the latest NGINX development branch now. Cheers!

[@oleksiistri8429]

So comprehensible explanation, thank you!

[@bitzerbutzer6053]

Very good descriptive explanation

[@starplatinum2008]

Flawless presentation
golden standard

[@iandaley2295]

This is an outstanding explanation

[@AbhishekTyagi]

Excellent presentation.

[@TimRiker]

Excellent presentation! Is the slide deck available?

[@lukehjo]

Lovely presentation.

[@JivanPal]

Why is this video unlisted...?

[@nicolekho7791]

Setting the Alt-Svc header as showed in the video didn't work, I used instead add_header Alt-Svc 'h3=":$server_port"; ma=86400'; as suggested in the NGINX blog and it worked

[@user-oj5ix7wu1f]

HTTP4?