UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Configure a proxy (that does not support socks) and select "Use this proxy for all protocols" in the "Use manually specified proxy configuration" section.
2. Access a web url that establish a secure websocket connection.
3. 

What is the expected behavior?
Expect secure websocket connection to be established correctly

What went wrong?
Websocket connection is not established. Fails with an error "net::ERR_SOCKS_CONNECTION_FAILED"

Did this work before? N/A 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 24.0 r0

RFC 6455 says "NOTE: Implementations that do not expose explicit UI for selecting a proxy for WebSocket connections separate from other proxies are encouraged to use a SOCKS5 [RFC1928] proxy for WebSocket connections, if available, or failing that, to prefer the proxy configured for HTTPS connections over the proxy configured for HTTP connections."

In my case, a socks connection to the server fails since it is not configured to run as a socks proxy. I would expect the browser to transparently use https connection, since the proxy does not act as a socks proxy.