HTTP/2
termweb devnetworking
A revision that multiplexes many requests over one connection and compresses headers, without changing what a request means.
It fixed the era's main waste - browsers opening several connections and queueing requests behind each other - by putting independent streams on one connection. The limitation is inherited from underneath: the streams are independent to the application and not to TCP, so one lost packet stalls all of them, which is the head-of-line blocking that QUIC was designed to remove. Its other legacy is operational, since a single long connection behaves differently through proxies than many short ones.
Also known as: h2