3 ms·
We will know over time. HTTP/3 is fixing all shortcomings of HTTP/2, which was pretty flawed. It uses UDP though, and UDP itself can be blocked by many firew
by ardit33 5y ago
We will know over time. HTTP/3 is fixing all shortcomings of HTTP/2, which was pretty flawed.
It uses UDP though, and UDP itself can be blocked by many firewalls, and folks/companies have to update firewalls and routers for it to work properly. So, that's its major weakness (eg. some workplaces block all egress UDP packets).
https://news.ycombinator.com/item?id=27402222 https://news.ycombinator.com/item?id=27402222
As the article says, HTTP3 is pretty fast when there are high latencies/high loss scenarios. It will be interesting to see how it performs in a mobile setting. 4G and 5G networks have their own/specific optimizations that are different than a desktop world. eg. http keep alives were never respected, etc. (connections would be closed if there was no continuous activity). But, given the test, it 'should' be much faster than http 1.1
One think is for sure: HTTP 1.1 is going to still be used, even 100 years from now. It is like FM Radio, which is both good enough for most cases, and very simple and convenient at the same time.
- josefx 5y agoI can't wait for all the HTTP/3 -> HTTP/2 -> HTTP/1 tunneling and other exploits that will appear in all the rushed implementations. We already saw how that worked with HTTP/2 and people tried to rush OpenSSL into adopting an experimental implementation of QUIC while Google was still hashing out the spec. . I would suggest disabling HTTP/3 for the next 10 or so years and give everyone else the chance to burn through the exploits.
- johncolanduoni 5y agoThankfully HTTP/3 didn’t change request/header semantics much from HTTP/2, at least nowhere near the level of the HTTP/1 -> HTTP/2 changes.
- ithkuil 5y agoDo you have a link at hand describing the main shortcomings of http/2 (that http/3 fixes)?