https://www.zdnet.com/article/cloudflare-google-chrome-and-firefox-add-http3-support/
By default, classic HTTP (a layer 7 protocol) uses TCP (a layer 4 protocol) as it’s base.
To solve speed issues with TCP and encryption with it, Google created SPDY, a protocol that fixed some of TCP’s problems. HTTP-over-SPDY protocol eventually became the official HTTP/2, which is now used on around 40% of all internet sites.
Later Google engineers realized they could do much better if make a totally new protocol. That’s how QUIC came to be, or “Quick UDP Internet Connections.”
HTTP/3 is QUIC implemented inside HTTP, replacing TCP and SPDY at the transport level. It was formally approved last October. HTTP/3 is currently used by only 3% of all internet websites.
5 Comments
Tomi Engdahl says:
DOS implications: “Both Google and Facebook have mentioned that their wide scale deployments of QUIC require roughly twice the amount of CPU than the same traffic load does when serving HTTP/2 over TLS.” https://daniel.haxx.se/http3-explained/
Tomi Engdahl says:
HTTP/3 (the third major version of the Hypertext Transfer Protocol used to exchange binary information on the World Wide Web, succeeding HTTP/2.)
https://www.cyberciti.biz has enabled it and is now waiting for mainstream browsers like FF, Chrome, and others to start sending traffic over http/3.
Tomi Engdahl says:
There is rather low HTTP/2 deployment at the moment, should we skip HTTP/2?
shell shockers says:
Thank you for your post. I have read through some similar topics! However, your post gave me a very special impression, unlike other articles. I hope you continue to have valuable articles like these or more to share with everyone!
word to pdf says:
Many inverters show light bulb as example load.
Usually this does not make sense because it’s more efficient to simply power a suitable low voltage led light from the low voltage side, there’s absolutely no advantage in losing so much efficiency boosting it to higher voltage AC.