TinkerHTTP/1.1, 4 connections: no file held back. Page in 2,060 ms.8,000 km · 14 trips to the shop · 1 resent · 2,060 ms
Chapter 6 of 7
One line, many files
The page arrives and names more files: styles, a script, a logo, two photos. Each one needs asking for.
This chapter: How do HTTP/1.1, 2 and 3 fetch many files, and what does a loss do to each?
About this chapter
You will learn
- HTTP/1.1 asks one file at a time per connection
- HTTP/2 sends them all on one connection
- HTTP/3 keeps one loss from stalling the rest
Words you’ll meet
- HTTP
- The language a browser and a site use to ask for and send files.
- Stream
- One request and its reply, sharing a connection with others.
- Head-of-line blocking
- A lost packet holding back everything behind it on the same connection.
- QUIC
- The transport HTTP/3 runs on: one handshake for connection and seal, a loss per stream.
Step 1 of 5
The page names 5 more files, fetched over . HTTP/1.1 asks one per connection at a time, opening extra connections.
Open the Waterfall tab.