Issue metadata
Sign in to add a comment
|
self-signed/expired certificate on websocket doesn't work anymore
Reported by
yong...@toremote.com,
Sep 7 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36 Steps to reproduce the problem: 1. try connect to a web site with self-signed certificate or expired certificate 2. Access warning and continue. 3. Create a websocket connection to the same host What is the expected behavior? The websoket connectin can connect What went wrong? It will not connect and report: WebSocket opening handshake was canceled Did this work before? Yes 60 Does this work in other browsers? Yes Chrome version: 61.0.3163.79 Channel: stable OS Version: 10.0 Flash Version: You can try https://startme.biz/view/rdp.html for testing
,
Sep 7 2017
You are probably looking for a change made after 483909 (known good), but no later than 483910 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/d5588cf4ffb5a932dcbfd87cd7761d390c790ea9..51a64d9d83edf4aa46f774f6bcd23f0271aa5366 Note : This is similar to issue#760708
,
Sep 7 2017
A workaround is that it appears that this RDP client supports disabling the use of a Worker. WebSocket connections from the main page are not affected by this issue.
,
Sep 7 2017
just double checked, this looks like only happens when the websocket connection is in a web worker. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pbomm...@chromium.org
, Sep 7 2017Components: Blink>Network>WebSockets
Labels: ReleaseBlock-Stable M-61 Needs-Bisect OS-Android OS-Linux OS-Mac
Status: Available (was: Unconfirmed)