9 ms·
This is how HTTP/2 works by design. There’s one TCP socket per host and the browser will make up to 6 parallel requests over it.
by jahewson 6y ago
This is how HTTP/2 works by design. There’s one TCP socket per host and the browser will make up to 6 parallel requests over it.
- chrismorgan 6y agoThis is nothing to do with HTTP/2. This is just keep-alive behaviour, which applies to HTTP/1.1 just as much as HTTP/2. Also the 6 is the maximum number of HTTP/1.1 connections most browser configurations will open per origin; HTTP/2 lets you have as many streams open on one connection as you like (up to 2³⁰ or 2³¹ if my memory serves me, but a billion ought to be enough for anyone).
- youngtaff 6y agoIt's possible to have two HTTP/2 connections to the same host. Where the host is a 3rd-party then credentialed (stylesheets, scripts, images etc) and anonymous connections (fonts, fetch etc.) will be separate
- megous 6y agoIt's also possible to have one connection to multiple origins with HTTP/2 (as long as they are on the same IP/port). I wonder if it's recommended though, since I've noticed this only on Safari so far.
- youngtaff 6y agoGuess what you're seeing is connection coalescing at work - they also need to share the same cert AFAIK