Computer Networks · Week 4–5
HTTP/1.1 vs 2 vs 3: multiplexing, streams, QUIC
00:00
Computer Networks • Week 4–5
01 / 13

HTTP/1.1 vs 2 vs 3: multiplexing, streams, QUIC

HTTP semantics evolve more slowly than HTTP transport behavior. HTTP/1.1 uses textual messages and traditionally relies on one request/response stream per TCP connection at a time unless multiple connections are used. HTTP/2 introduces binary framing, multiplexed streams, HPACK header compression and prioritization features. HTTP/3 maps HTTP semantics onto QUIC streams.

StackShade deck
COURSE CONTENTS

HTTP/1.1 vs 2 vs 3: multiplexing, streams, QUIC

01How the Internet Works + OSI ModelWeek 1 · 4 topics0/4
02Physical & Data Link LayersWeek 1–2 · 5 topics0/5
03Network Layer: IP & RoutingWeek 2–3 · 6 topics0/6
04Transport Layer: TCP & UDPWeek 3–4 · 5 topics0/5
05Application Layer: HTTP, DNS & FriendsWeek 4–5 · 6 topics0/6
06Security & Troubleshooting ToolkitWeek 5 · 5 topics0/5