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!

[@MikkoRantalainen]

Having public IPv4 address for your client machine is going to be even more valuable because UDP traffic works without any issues if you have public IPv4 address. If you have to use NAT, good luck.

[@MikkoRantalainen]

21:58 I would have loved to see every packet direction with it's own arrow. The double ended arrow "(key exchange and ecrypted session setup)" is missing lots of important details about why TCP latency hits that bad and why UDP can improve things. And you should also mention TLS Session Resumption (session ids and session tickets) and TCP Fast Open (TFO) because those reduce latency a lot for repeated connections which is the situation that QUIC / HTTP/3 is used, too. Otherwise you're comparing first connection of HTTP/2 to repeated connection using HTTP/3 which seems a bit dishonest. The most important part of HTTP/3 is to avoid head-of-line blocking and that really affects only the situation where network is flakey enough to lose random packets.

[@bitzerbutzer6053]

Very good descriptive explanation

[@starplatinum2008]

Flawless presentation golden standard

[@lukehjo]

Lovely presentation.

[@AbhishekTyagi]

Excellent presentation.

[@TimRiker]

Excellent presentation! Is the slide deck available?

[@MikkoRantalainen]

I expect a lot of company level firewalls are going to block QUIC / HTTP/3 because it's encrypted traffic over UDP. There's no way the firewall can inspect any of that data and UDP traffic is harder to monitor than TCP traffic in the first place. And because every server supporting HTTP/3 will also support HTTP/2, the end users are not going to see major hit even if HTTP/3 is not allowed. And to avoid smuggling encrypted data over port 53, I wouldn't be too surprised to see that non-plaintext communication over port 53 would be totally blocked, too.

[@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

[@JivanPal]

Why is this video unlisted...?

[@iandaley2295]

This is an outstanding explanation

[@LucasWolf-o6o]

HTTP4?