5 ms·
Be that as it may, this still doesn't seem like the big deal that so many people are making it out to be. Support for HTTP/1.1 and HTTP/2 won't be going anywher
by jeffparsons 4y ago
Be that as it may, this still doesn't seem like the big deal that so many people are making it out to be. Support for HTTP/1.1 and HTTP/2 won't be going anywhere fast, so legacy software can keep doing what it's always done, can't it?
HTTP/3 can be for people/applications that value what is has to offer, and can largely be ignored otherwise.
- superkuh 4y agoHTTP/1.1 is the last good HTTP that is designed for a human persons' needs instead of corporate persons needs. It'll be phased out of the megacorp browsers as soon as their services no longer require it. Likely they'll say it's for security reasons. And they won't be wrong (about their use case). They'll just be ignoring humans because human projects don't earn them money.
- Macha 4y agoNote: My post was talking about Name Constraints in TLS certs and not HTTP versions. The edit window is expired so I can no longer clarify there.