5 ms·
Intetestingly (or rather not surprising at all?) http3 is eating away the http2 traffic, while http1 just stays on a very slow decline. Since http1 webservers
by ascar 3y ago
Intetestingly (or rather not surprising at all?) http3 is eating away the http2 traffic, while http1 just stays on a very slow decline.
Since http1 webservers are usually stuck there for a (more or less) good reason, they won't be converting to http3 anytime soon, while already more modern webservers are easier to upgrade from http2 to 3.
- oblio 3y ago> Intetestingly (or rather not surprising at all?) http3 is eating away the http2 traffic, while http1 just stays on a very slow decline. HTTP1: the OG, meant for a much smaller individual scale. So great even today for smaller websites. Where smaller right now, with modern hardware, can actually still mean hundreds of requests per second and millions per day... HTTP2/HTTP3: BigCorp optimization primarily for problems they're facing and not that many others are. So viewed through this lens it's clear what's happening. BigCorps are just moving from HTTP2 to HTTP3 and mom and pops don't give a crap, HTTP1 is good enough.
- charcircuit 3y agoHTTP2 is useful even if you just want to show multiple images on a page. For HTTP1 you have to add all of your images to a sprite sheet to avoid sending a lot of requests.