UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36

Steps to reproduce the problem:
1. At first you need to have a misconfigured server with certificates file without concatenation of chained authority, but with WebSocket support
2. Connect to the server through HTTPS. For some reason Chrome will not alert the end-user and the browsing will be possible even without the certificate chain present.
3. However, the handshake through wss:// will fail, giving no more informations than "Handshake Failure"

What is the expected behavior?
I guess the expected behavior would be to:
A/ Reject both HTTPs and Websocket connections as they are unsafe
B/ Accept both HTTPs and Websocket connections as they are safe enough

Having only a part of the communication allowed seems really strange in my opinion

What went wrong?
The website seems to work properly, except for the websocket which fail to connect to the server.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 54.0.2840.98  Channel: n/a
OS Version: OS X 10.12.1
Flash Version: Shockwave Flash 24.0 r0