Issue metadata
Sign in to add a comment
|
Loading Loop after blocking a https connection with a TCP reject
Reported by
itbetrie...@googlemail.com,
Apr 9 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Example URL: Steps to reproduce the problem: 1. blocking https connections with tcp reject 2. use chrome version 65.0.3325.181 In our case we are blocking sites with bluecoat proxy sq without ssl interception. Proxy Version: SGOS 6.5.10.4. The proxy server cannot send a http code error because there is no ssl interception enabled. Instead of this the proxy send a tcp reject before the ssl handshake. What is the expected behavior? Chrome try to reload the ressource as much as possible in a endless loop. With some clients we get about 100-200 connections per second What went wrong? Chrome should display a error message like "cannot establish secure connection" instead of endless connecting in a loop. Did this work before? Yes Chrome version: 65.0.3325.181 Channel: stable OS Version: 10.0 Flash Version:
,
Apr 9 2018
,
Apr 10 2018
itbetrieb.vhw@ Thanks for the issue. Request you to provide a test URL where this issue can be reproduced which will help in further testing. Also request 'Internals>Network' team to look into this issue and help in further triaging. Thanks..
,
Apr 11 2018
[+davidben]: Was that auth-loop around in Chrome 65?
,
Apr 11 2018
Yeah, that's the auth loop. :-( It will be fixed in 67 and mitigated in 66. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by itbetrie...@googlemail.com
, Apr 9 2018