HTTP 1 Vs HTTP 2 Vs HTTP 3!

Animation tools: Adobe Illustrator and After Effects.

Checkout our bestselling System Design Interview books:

ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.

[anastasiaviva]

If only explanations could win Oscars… Thank u for delivering such high quality content!!!

[AqgvPr-hqvu]

The thumbnail was so complete and beautiful that i could not press the video and automatically press the like button.

[vylbird]

One "Fun" annoyance: You can't use QUIC without a TCP fallback, because a great number of company firewalls will block any port that isn't expressly allowed (as is sensible), and they generally don't allow UDP. Chrome will always open both HTTP3 and HTTP2 connections when trying to reach a host, so if the 3 fails it can fall back to 2 in no time at all.

[shellcatt]

This video is so packed, if there were a quiz at the end of it I'd definitely fail at it, more than once :D

[upgrade]

great way of explaining how the web works

[quillaja]

HTTP/4: The AI powered server pushes ads and recommended paid content directly to your devices without the slowdown of waiting for you to request them. Efficiently uploads your private information with 0 round trips to ask for permission.

[bartosz.]

Me: I understand HTTP fairly well
ByteByteGo: nope

[arithex]

Q: How many software engineers does it take, to send a message from one computer to another?
A: Apparently many millions of us, over a period of about 30 years.

[Azcraz]

You should EQ filter out some of the low end bass frequencies of your voice (aka high-pass). The voice audio is "boomey" when listening to the video on capable speakers. Great video, love the information and presentation!

[georgehelyar]

The host header was a big deal in http 1.1. Before that you could not host multiple websites on the same ip, so if you were a web host you would only do separate paths for separate sites, or have to give each site their own server. Remember geocities?

[km]

Simple way of getting complex information. It is a perfect content. Subscribed. Well done guys !!!

[KMegahertz]

I've never understood why HTTP was designed to close the connection after requesting a single object. I do understand compute resources were much more constrained than they are today, so keeping tens of thousands of TCP connections open might be problematic, but even then I figured it was better to open a connection, request all the objects for a page, then at that point maybe terminate the connection.

[sudorandom]

When talking about QUIC integrating with TLS 1.3 the narrator actually says "TCP 1.3" which is not correct 😅

This is a great summary though, I love the visuals

[mrbig]

1:20 actually we didn't use TLS back in the times of HTTP1.0 because it used too much of the precious CPU cycles. Unless you had to do something really security critical thing you just opted for the cheap solution. Also there wasn't much to be stolen on the internet back then :)

[amirsaid]

Thank u, Great explanation as always 👏🏻

[lohphat]

QUIC breaks content inspection at the f/w and local endpoint security solutions. Many orgs just block it outright until security catches up.

[kevinmoy]

the visual aid goes kinda crazy with it

[SirusStarTV]

HTTP 1.1 is text based protocol, each header is separated by CRLF "carriage return and line feed" symbols like in Windows text files, in programming languages written like "\r\n" in string literal.
After the last header you need to add additional CRLF to define the start of body of http request or response, the length of data in a body is expected to be set by "Content-Length" header. Example:
POST /api/endpoint HTTP/1.1 *CRLF*
Content-Type: application/json *CRLF*
Content-Length: 34 *CRLF*
*CRLF*
{ "someJsonKey": "someJsonValue" }

[BlackbirdDH]

Awesome video .... great visualizations.

[swamihuman]

- Thx.
- Well done: clear/concise; and informative. Excellent graphics, too.
- Keep up the great content...