Google already enables and uses its experimental protocol “QUIC” on its websites in Chrome browser, today, the company has gone ahead and integrated it along with HTTP/3 into the Canary version.
Google obsessed with speed, announced in 2013 that they’re experimenting with QUIC, pronounced as Quick and its full form is Quick UDP internet connections.
For the unknown, QUIC, “is an early-stage network protocol” that “runs a stream multiplexing protocol over a new flavor Transport Layer of Security (TLS) on top of UDP instead of TCP”.
The company says, to improve the network performance we need to decrease the number of round tips and feels its difficult with the protocols that rely on Transmission Control Protocol (TCP), Google says their QUIC does that by combining “a carefully selected section of techniques”.
In 2015, Google provided an update on QUIC by saying their data shows ” QUIC provides a real performance improvement over TCP” and says it’s possible because of their UDP-based protocol’s ” lower latency connection establishment, improved congestion control, and better loss recovery”.
Since then we haven’t heard back from the company on the Protocol, today, Robin Marx, who works on Webperf/HTTP3/QUIC, announced on twitter that Chrome Canary is the first browser available with integration of QUIC and HTTP/3.
To test their support right away in Google Chrome browser
1. Run the latest Chrome Canary with below command-line flags
--enable-quic --quic-version=h3-23
2. Visit quic.rocks:4433 or third-party site LiteSpeed tech, to notice former demo site to show a message you have successfully loaded the site using QUIC, and the devtools console for Network tab shows protocol as “http/2+quic/99”, Robin says it is actually http3 in disguise.
If you now search for Quic on Google, you’ll also notice search results with support articles from Bitdefender and ESET offering instructions on how to disable the protocol in Chrome browser as it was known to break web protection/ Parental Controls offered by security products in Chrome.
If you’ve noticed any issues with QUIC, visit Chrome://flags page, search for it and disable, relaunch the browser to see it resolves the issue.
