Issue metadata
Sign in to add a comment
|
Search does not work (I use google search). I can use it on Firefox, but not in Chrome.
Reported by
veljov...@gmail.com,
Apr 10 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 Example URL: Steps to reproduce the problem: 1. 2. 3. What is the expected behavior? What went wrong? I can not use google search on chrome. When I try to search for something, I have to endlesly wait, and then I get the message "ERR_QUIC_PROTOCOL_ERROR" and "The webpage at https://www.google.ba/search?*** might be temporarily down or it may have moved permanently to a new web address." It works fine in Firefox. I also can not open any google site (google.com, google.ba). I can open Gmail or G+. Also it is not possible to use "Report an issue" within chrome, with the same message. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? Yes Chrome version: 57.0.2987.133 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0
,
Apr 11 2017
Thank you for providing more feedback. Adding requester "bnc@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 13 2017
This looks like a Network stack issue.
,
Apr 13 2017
Thank you for the log. Seems like a large number of QuicSessions are failing with QUIC_NETWORK_IDLE_TIMEOUT, each resulting in a user-visible ERR_QUIC_PROTOCOL_ERROR on the corresponding UrlRequest. I thought QUIC errors should not be visible to the user, since there is always a TCP job racing.
,
Sep 29 2017
@bnc - A friendly ping. Is there any update on this issue. Thanks!
,
Sep 29 2017
Ryan, could you please take a look at this? Could it be a firewall that allows QUIC connection establishment but then blackholes traffic?
,
Sep 29 2017
bnc: Agreed. Looks like a middlebox that is messing with QUIC traffic. We're currently running an experiment that we'd like to turn on by default once we confirm that it's working as expected. Can you run Chrome with the following arguments and see if that solves the problem? --enable-quic --force-fieldtrials="QUIC/FlagEnabled" --force-fieldtrial-params="QUIC.FlagEnabled:mark_quic_broken_when_network_blackholes/true/retry_without_alt_svc_on_quic_errors/true"
,
Sep 30 2017
I tried this several times and it works fine every time. Thanks a lot.
,
Sep 30 2017
Thank you for providing more feedback. Adding requester "rch@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 6 2017
veljovici@ Thanks for the confirmation. As per comment #9, as the issue is solved, can we close this issue? Please confirm. Thanks..
,
Oct 10 2017
Dear Sirs I can confirm that the issue is solved, and you can close it. I hope that it will be turned on by default one day. Best regards Ibrahim Veljovic
,
Oct 10 2017
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 10 2017
Re #12: Thank you for your response. I'm merging this issue into the one corresponding to the new feature mentioned in #8. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by b...@chromium.org
, Apr 10 2017