upvote
Because any HTTP spec after 1.1 is incredibly complicated. You can implement HTTP/1 in half a day, and HTTP/1.1 in a day. But HTTP/2 will probably take you a month and HTTP/3 might take something like 6 months.
reply
It boggles my mind that people are patting themselves on the back for staying on old tech stacks and using a discovered vulnerability as further justification of their decision to stay on h1.1. The response is to patch and move on if your environment requires h2; many large orgs these days use microservices which use h2 (grpc) as its network.

There are many legitimate use cases for h2 (eg bidi streaming, latency improvements) and h3 (eg seamless network switching).

If you don’t need these features and just serve vanilla text webpages that’s also fine to just use h1.1. Blanket statements that h1.1 is better is just, wrong. Context is important on choosing what’s best for your environment.

reply
> If you don’t need these features and just serve vanilla text webpages that’s also fine to just use h1.1.

Which, to be fair, is most sites.

reply
You forgot about all the networking hardware and software those run on. The difference is negligible.
reply
Do you realize that no one writes toy HTTP implementations from scratch? I get that you might have a "suckless" mindset but that's just not how the real world works.
reply
That's not the point. The point is that the simpler the protocol is to implement, the simpler it is to validate and harden the implementations. A HTTP/1.1 implementation can be 10x to 30x smaller than an equivalently well-rounded HTTP/3 implementation.
reply
A simpler protocol has less surface area for vulnerabilities. I think GP was just using that as an expression of this.
reply
HTTP 1.1 has enough complex behaviors at the edge that the idea of implementing it in a day, correctly, is wildly laughable.
reply
It's debuggable. I can wireshark it and understand everything. I can even speak to HTTP servers directly with a telnet client and fetch pages. I can write microcontroller code in C that issues REST API requests. Pure TCP, nice to work with, no multiplexed UDP hex craps.

Simple is good.

reply
~25 years of hardening.
reply