New issue
Advanced search Search tips

Issue 664738 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 657791
Owner: ----
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

wss connection fail (ERRR_INSECURE_RESPONSE) on MacOS Sierra version 10.12.1

Reported by sylvain....@consoftinc.com, Nov 12 2016

Issue description

Chrome Version       : 54.0.2840.98 (64-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: OK
    Firefox: OK
         IE:

Error occur on a iMAC, Tested on other PC (using Chrome, Firefox, Opera and IE) everything was OK. I have tested on another iMAC using same Chrome version, everything was OK.

What steps will reproduce the problem?
(1) access www.websocket.org/echo.html
(2) enter wss://www.interviewandsupport.com:8080/ws
(3) press Connect
(4) get Fail (ERR_INSECURE_RESPONSE)

What is the expected result?
Should get a secure websocket connection

What happens instead?
Get an ERR_INSECURE_RESPONSE (occur on one iMAC). 

Please provide any additional information below. Attach a screenshot if
possible.

I tried to clear cache, history, reinstall Chrome still same error.

 
net-internals-log.json
55.0 KB View Download
Labels: TE-Hardware-Dependency
As Chrome HYD team do not have iMac to test this issue,could anybody please look into this issue.

Thank you.


Comment 2 by ajha@chromium.org, Nov 22 2016

Labels: M-54

Comment 3 by tkent@chromium.org, Dec 14 2016

Components: Blink>Network>WebSockets
Labels: Needs-Feedback
What's the version of Mac OS on your iMac?

This might be dup of  bug 657791 .
I am using MacOS Sierra version 10.12.1

Labels: OS-Mac
Summary: wss connection fail (ERRR_INSECURE_RESPONSE) on MacOS Sierra version 10.12.1 (was: wss connection fail (ERRR_INSECURE_RESPONSE) )
Then you might be suffering from the same issue described in  bug 657791 . Please take a look at it.
Hello Tyoshino,

Yes, it seem to be identical issue. Also, I did update my Chrome from version 54.0.2840.98 to 55.0.2883.95 and the issue did disappear. 

Do you know what was change to fix it? 

Also, we can close this isse.

Thanks,

Sylvain
Mergedinto: 657791
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment