Enable QUIC protocol in Google Chrome

Oh Dear monitors your entire site, not just the homepage. We crawl and search for broken pages and mixed content, send alerts when your site is down and notify you on expiring SSL certificates.

Start your free 10 day trial! »

Profile image of Mattias Geniar

Mattias Geniar, July 29, 2016

Follow me on Twitter as @mattiasgeniar

Google has support for the QUIC protocol in the Chrome browser, but it’s only enabled for their own websites by default. You can enable it for use on other domains too – assuming the webserver supports it. At this time, it’s a setting you need to explicitly enable.

To start, open a new tab and go to chrome://flags/. Find the Experimental QUIC protocol and change the setting to Enabled. After the change, restart Chrome.

chrome_quic_support_setting

To find out of QUIC is enabled in your Chrome in the first place, go to chrome://net-internals/#quic.

In my case, it was disabled (which is the “default” value).

chrome_quic_internals_enabled

After changing the setting to enable QUIC support and restarting Chrome, the results were much better.

chrome_quic_internals_status_enabled

On the same page, you can also get a live list of which sessions are using the QUIC protocol. If it’s enabled, it’ll probably only be Google services for now.

chrome_quic_internals_sessions

I’m working on a blogpost to explain the QUIC protocol and how it compares to HTTP/2, so stay tuned for more QUIC updates!



Want to subscribe to the cron.weekly newsletter?

I write a weekly-ish newsletter on Linux, open source & webdevelopment called cron.weekly.

It features the latest news, guides & tutorials and new open source projects. You can sign up via email below.

No spam. Just some good, practical Linux & open source content.