The default QUIC setting has been changed to "disabled" in Chrome

[Dmitri Tikhonov]

Hi all,

The default QUIC setting has been recently changed to "disabled" in Chrome (60.0.3112.78).  What is the reason behind this change and when can we expect for the default to be set to "enabled" again?

Thank you,

  - Dmitri Tikhonov.

[Ryan Hamilton]

I don't think QUIC is disabled by default in chrome 60. We do, however, continue to run hold-back experiments in QUIC will be disabled for a small set of users chosen at random on startup. Is that perhaps what you're seeing?

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+unsubscribe@chromium.org.
To post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Dmitri Tikhonov]

Perhaps, but it is not just me.  Several of our customers report that QUIC is no longer used when users connect to their LiteSpeed [1] web servers (or web proxies).  A few tests in the office show that the default QUIC setting is now "disabled."  Changing it from "default" to "enabled" turns QUIC on and it works as expected, but since most Chrome users do not change the settings, they would no longer reap QUIC benefits.

The change seems more than random and I wanted to find out what's up.  How can one tell if he is a part of the experiment that causes QUIC to be turned off?  Also, how is this behavior controlled: is there a main Google Chrome config server that Chrome talks to at start-up?

  - Dmitri.

1. We announced QUIC support a couple of weeks ago in the new releases of LiteSpeed Web Server and LiteSpeed ADC.

On Monday, July 31, 2017 at 6:32:32 PM UTC-4, r...@chromium.org wrote:

I don't think QUIC is disabled by default in chrome 60. We do, however, continue to run hold-back experiments in QUIC will be disabled for a small set of users chosen at random on startup. Is that perhaps what you're seeing?

On Mon, Jul 31, 2017 at 2:05 PM, Dmitri Tikhonov <dtik...@gmail.com> wrote:

Hi all,

The default QUIC setting has been recently changed to "disabled" in Chrome (60.0.3112.78).  What is the reason behind this change and when can we expect for the default to be set to "enabled" again?

Thank you,

  - Dmitri Tikhonov.

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.

[Ryan Hamilton]

Hm. So to confirm the default, you would to to:

  chrome://flags/#enable-quic

From a fresh install of Chrome. I just did so and verified that it shows "Default"

To check if you were part of the experiment, you could go to chrome://net-internals, stop capturing, and see what shows up in the active field trials list. I did that on a fresh install and did not see the QUIC experiment, which is problematic. Doing some digging, and it looks like the server-side config which controls the QUIC experiment has a problem. I've checked in a fix to this and it will probably propagate over the next few hours.

Thank you SO much for reporting this (and not letting me convince you that you were part of the hold-back! :>)

And congratulations on the LightSpeed + QUIC launch. That's fantastic!

Cheers,

Ryan 

To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+unsubscribe@chromium.org.

[Dmitri Tikhonov]

It is my pleasure.  I am glad we will soon be back to normal.

And thanks!  We at LiteSpeed are happy to support QUIC and to help improve UX!

Happy QUICing,

  - Dmitri.