HTTP/1.1, HTTP/2, HTTP/3 in brief
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
understand versions and connection reuse at a high level.
Planned topics
- HTTP/1.1 is text based. Connections are kept alive and reused, but requests on one connection wait in line.
- HTTP/2 is binary and multiplexes many requests over one connection, and compresses headers.
- HTTP/3 runs over QUIC (on UDP) and avoids one lost packet stalling everything.
- Your controller code does not change between versions; the server and client negotiate it.
- Opening a new connection is expensive (TCP and TLS handshakes), so reuse matters.
Draft outline details
Demonstration
a diagram of three requests: HTTP/1.1 queued on one connection, HTTP/2 interleaved on one connection.
Check your understanding
What problem does HTTP/2 multiplexing reduce?
Show answer
Requests waiting in line on one connection.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.