ERR_QUIC_PROTOCOL_ERROR loading page in airplane mode |
|||||
Issue descriptionApplication Version (from "Chrome Settings > About Chrome"): 63.0.3219.0 Android Build Number (from "Android Settings > About Phone/Tablet"): NHG470 Device: Pixel Steps to reproduce: 1) enable Data Saver 2) Set flags to force HD Previews (not sure if this is needed) 3) Turn on airplane mode 4) Enter cnn.com into the URL bar Observed behavior: I saw a network error page with ERR_QUIC_PROTOCOL_ERROR (screenshot attached). Expected behavior: I should have seen the "You are offline" dino page instead, since I was in airplane mode. My theory is that this has to do with Flywheel. The problem of course is that if a user loses connectivity, we need to show the dino page (with the option to download the page later, etc.) and not a network error page. I think this problem could be affecting many users, on the assumption that users losing network connectivity in Flywheel target countries is a frequent occurrence.
,
Sep 25 2017
I have been trying to repro this, but have not succeeded. It's possible that the QUIC failed to read from an already connected socket because of connectivity loss. However, the error was incorrectly attributed (due to some racing) to the protocol/socket layer, instead of the absence of the network connectivity. I can not see why this bug would be specific to QUIC or to data saver. May be offline team can consider showing the offline button on a more variety of error codes (including protocol/socket errors) if the device is found to not have the connectivity? dimich@, thoughts?
,
Sep 27 2017
Do we have any metrics on how often this might be happening?
,
Dec 1 2017
tbansal@: ping.
,
Dec 1 2017
Reassigning to dimich@. One possibility is to show the offline button when the error code is ERR_QUIC_PROTOCOL.
,
Dec 5 2017
,
Jan 24 2018
Refreshed during triage.
,
Jan 24 2018
,
Jan 24 2018
Moving to UI>Browser>Offline to consider the possibility of showing offline action buttons on more net errors. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mdw@chromium.org
, Sep 22 2017