At over thirty years old, HTTP is still the foundation of the web and one of the Internet’s most popular protocols—not just for browsing, watching videos and listening to music, but also for apps, machine-to-machine communication, and even as a basis for building other protocols, forming what some refer to as a “second waist” in the classic Internet hourglass diagram.
What makes HTTP so successful? One answer is that it hits a “sweet spot” for most applications that need an application protocol.
HTTP/2 is pretty well supported now, HTTP/3 sound promising in standardising QUIC.
MASQUE sounds neat but also potential security considerations.
Meanwhile, cannot help but feel there is alot of scope creep happening and that HTTP/1.1 remains the most practical point in the spec.