Customer noticing intermittent connection loss in Chrome 50 |
||||
Issue descriptionCustomer noticed that since they got version 50 some of the desktops are periodically having trouble connecting to some google websites. Background: - Customer's environment does MiTM SSL based content inspection (Bluecoat) - Customer environment doesn't allow DNS resolution... requests have to go to proxy - They have atleast 2 proxy end points - We have net-internals and wireshark captures which I'll share in a drive folder - Based on initial investigation by chrome team it looks like the proxy server is killing connection in late stages of connection setup. It pointed at some problem on the proxy side. - We also see 407s with NTLM being mentioned. Its not clear how proxy auth is setup there, and if there could be other NTLM related failures involved.
,
May 14 2016
In the working json file, we also note that the proxy had been marked as bad by chrome. Not sure why.
,
May 17 2016
As mentioned over email, this is still blocking on net-internals from a less ludicrous revision range.
,
May 17 2016
It's also blocking on checking with the customer to make sure their proxies are all up-to-date, given the report that this is sporadic.
,
May 20 2016
Bluecoat folks tell me there's a bug that was fixed in their ProxySG 6.5.8.7 release, from back in November. Please ask the customer to make sure their proxies are up-to-date and see if the problem still occurs. I'm going to go assign this to royans@ as we have several pending requests for information here.
,
Jun 1 2016
Sorry about the delay here. The customer was able to work with bluecoat and resolve the issue. Closing the bug.
,
Jun 1 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by royans@chromium.org
, May 14 2016Labels: -Pri-3 Pri-2