| Do you know maybe whether there are similar adoption rates in HTTP/3? As someone that implemented http/1.1 almost feature complete [1], I think that the real problem on the web is the missing of a testsuite. There needs to be a testsuite for http that both clients and servers can test against, and that is not tied to internal codes of a web browser. I say this because even a simple spec like 206 with multiple range requests literally never is supported by any web server. Even Nginx, apache or google's own dns over https servers behave differently if the request headers expect multiple response bodies. Let alone the unpredictability of chunked encodings, which is another nightmare. I really think that there should be an official testsuite that is maintained to reflect the specifications, similar to the intention of the (meanwhile outdated) acid tests. Adoption rates to new http versions will always stay low if you implement it for months exactly as the spec says, just to figure out that no real world webserver actually implements it in the same way. [1] https://github.com/tholian-network/stealth/blob/X0/stealth/s... |