Question about the QUIC protocol in Google Chrome

F5F Stay Refreshed Software General Software Question about the QUIC protocol in Google Chrome

PrestonNguyen
Member

218

11-30-2016, 12:47 PM

Google employs the QUIC protocol by default. Can it be turned off using flags without causing major issues?

PrestonNguyen

11-30-2016, 12:47 PM #1

Google employs the QUIC protocol by default. Can it be turned off using flags without causing major issues?

nugrr
Member

11-30-2016, 01:34 PM

This change is expected to enhance streaming traffic performance according to the provided definition.

nugrr

11-30-2016, 01:34 PM #2

This change is expected to enhance streaming traffic performance according to the provided definition.

TurritaSC
Member

156

12-03-2016, 06:14 AM

Over the last couple of months, this issue has occurred occasionally:
Spoiler
I came across an article -
https://support.umbrella.com/hc/en-US/kb?id=20CC5D1C0
For testing, I turned off QUIC in Google Chrome today. The error wasn't present yet (it appeared randomly, but consistently). I didn't observe any other significant changes when QUIC was disabled.
*I rely on DoT and DoH to secure DNS traffic.*

TurritaSC

12-03-2016, 06:14 AM #3

TastyTicTac
Junior Member

12-05-2016, 02:59 AM

A day has gone by since we turned off the flag above, and everything worked fine.

TastyTicTac

12-05-2016, 02:59 AM #4

A day has gone by since we turned off the flag above, and everything worked fine.

GodZenik
Member

242

12-07-2016, 08:16 AM

Turning off that protocol might resolve the issue with packet drops. The traffic should switch back to TCP, which I believe. As long as your connection is reasonably fast, it should work fine.

GodZenik

12-07-2016, 08:16 AM #5

Turning off that protocol might resolve the issue with packet drops. The traffic should switch back to TCP, which I believe. As long as your connection is reasonably fast, it should work fine.

V_Angel29
Member

187

12-13-2016, 04:14 PM

Yes, HTTP/1.1 and HTTP/2 function properly.
Spoiler

V_Angel29

12-13-2016, 04:14 PM #6

Yes, HTTP/1.1 and HTTP/2 function properly.
Spoiler