Add ability to manage chrome flag settings at chrome://flags from the GSUITE for education admin console for deployments of chromebooks ex. disable Experimental QUIC protocol which is allowing students to bypass content filtering.
Reported by
kevin.sa...@midwayisd.org,
Feb 14 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. chrome://flags 2. Expiremental QUIC protocol 3. Disable What is the expected behavior? GSUITE admin can manage chrome flags settings from the admin console by going to manage devices -> chrome management -> user settings and adjusting the chrome flag settings by OU. What went wrong? Currently, the Experimental QUIC protocol is set to Default which is enabled. This protocol is allowing traffic to bypass our content filtering appliances. Did this work before? N/A Chrome version: 56.0.2924.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 Adding this feature will allow admins to globally change the default of these flags from the console which is preferred to a manual process on large deployments.
,
Feb 20 2017
Our issue is with Chrome on Chromebooks.
,
Feb 20 2017
The QuicAllowed policy is supported under Chrome OS too, as is documented in the policy description. There was, apparently, a problem with applying the policy in versions prior to 57. But this was fixed in 57.0.2987.50: see issue 658454 .
,
Jul 5 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by emaxx@chromium.org
, Feb 20 2017Components: Internals>Network>QUIC
Labels: Enterprise-Triaged