Did HTTP/1.0 always open a new TCP connection for every resource?
HTTP/1.0 commonly closed the connection after a response, but some implementations added an explicitly negotiated Keep-Alive extension. HTTP/1.1 made persistent connections the default, so the simplified claim that all HTTP/1 traffic always used one connection per file is inaccurate.
Answered in
HTTP/1 to HTTP/3: Persistent Connections, Multiplexing, and QUICHow HTTP moved from sequential HTTP/1 exchanges to HTTP/2 streams and HTTP/3 over QUIC, including the transport limits each version keeps.
Read the full analysisOther questions this article answers
More network protocols questions
- Does HTTP/2 eliminate every form of head-of-line blocking?
- Does HTTP/3 make packet loss irrelevant?
- Does HTTP/2 multiplexing prevent TCP head-of-line blocking?
- Does one lost QUIC packet stop every HTTP/3 stream?
- Is HTTP/3 always faster than HTTP/2?
- Does DNS happen before every HTTP request?
- Is UDP an unreliable protocol with no congestion control?
- Is QUIC just UDP with encryption?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Network Protocols beat.