Issue metadata
Sign in to add a comment
|
Unwanted very huge traffic generated from end users toward clients1.google.com.
Reported by
bjadhav1...@gmail.com,
Nov 1
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Steps to reproduce the problem: 1. open chrome browser 2. Without browsing traffic auto generating. 3. Internet surfing from chrome browser What is the expected behavior? Our environment end user system generate a log of traffic to this url (clients1.google.com) and it affects to proxy performance (slow response through clients as well as proxy service stop). Why the traffic going to clients1.google.com?, any suggestion ? What went wrong? Generated traffic is legitimate or not. Did this work before? No Chrome version: 70.0.3538.67 (Official Build) (64-bit) Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 31.0 r0 Please provide salutation on the same ASAP
,
Nov 1
,
Nov 2
,
Nov 2
Hi Team, Please find attached networks logs as requested by you. Waiting for your feedback. Regards, Bharat Jadhav
,
Nov 2
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 2
You'll need to attach the files via the bug reporting tool not via email. They don't get added to the bug report if you send them via email.
,
Nov 2
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 2
Thanks for the log! Looks like we're trying (legitimately) to connect to clients1.google.com (various features in Chrome hit that URL), and the proxy is giving back an auth request (using basic auth). When we provide it, the proxy responds once again with a basic auth challenge and the process loops, which is what's causing the mess of connection attempts. Adding proxy and auth folks to investigate. (I filtered the NetLog on clients1.google.com.)
,
Nov 2
I bet the elided 10 bytes are "Basic 0g==". This is fixed on M71, but unfortunately the merge was rejected due to it existing prior to M69. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Nov 1