4 ms·
Yep, just like IPv4 didn't, HTTP/1 and H2 aren't going anywhere anytime soon.
by ignoramous 3y ago
Yep, just like IPv4 didn't, HTTP/1 and H2 aren't going anywhere anytime soon.
- wraptile 3y agoIPv4 is not going away because it's valuable (as in limited supply creates a market). HTTP 1.1 is already unusuable in modern web as you'll be instantly blocked by cloudflare and gang. HTTP2 is likely to follow in near future as replacing it will be much easier than replacing http1.1.
- re-thc 3y agoAdoption was also slow because there were lots of legacy switches and routers that did not support it. Upgrades took a long time.
- bheadmaster 3y ago> IPv4 is not going away because it's valuable (as in limited supply creates a market). That's what I've been telling my bros about crypto.
- wraptile 3y agoI'm not sure you understand. IP scarcity means they are more valuable in the web automation context. IPv6 availability will make it harder to "price" web automation -> more bots online -> more captchas and privacy invasions. That's a real challenge that is hard to solve despite your snarky comments.
- bheadmaster 3y agoThe IPv4 address scarcity means that bots cause a lot more collateral damage, because if your neighbor runs a bot from home, you'll most likely get banned too. Yeah, there's value in convenience of being able to block misbehaving IPv4 addresses. There's also value in burning CPU cycles to produce a transaction on a blockchain. Make of it what you will.
- Ekaros 3y agoHTTP2 is probably first one to go or be replaced. You can live without it or update it to whatever next thing.
- j16sdiz 3y agonit: It is HTTP/1.1 . HTTP/1.0 have long gone
- BenjiWiebe 3y agoI'm pretty sure I saw HTTP/1.0 in a PLC's status page recently.
- Twirrim 3y agoSadly, 1.0 is _still_ around. Rare, but it happens. I remember being gobsmacked several years ago that F5 LBs only supported HTTP/1.0 health checks. Doing HTTP/1.1 health checks required writing one specifically for it. Something the community had got sorted a long time ago.