TechEcho

(I'm the Chromium dev who triaged the bug this morning) This title is misleading. There's a bug when the SSL handshake for a WebSocket encounters an error, such as an invalid server certificate. This obviously sucks for developers, but for production sites which should not have SSL handshake errors, it should not be an issue.

This is one of the reasons corporates still use IE. Its easy to control and QA for stuff like this.<p>Heads roll when 1500 people can't work.

It's not predictably happening with _all_ websocket server implementations. I tried with node.js using a combination of https and ws modules. That worked. We crashed Chrome using em-websockt and netty, though.

A quick way to test this is to use:<p><a href="http://websocketstest.com/" rel="nofollow">http://websocketstest.com/</a>

I tested this with an em-websocket (Ruby) server using SSL and after I updated to Chrome 19 (OS X 10.7.3) it no longer works.

I just tested this under OSX and had no problem, so this is probably Windows-only.

This should get fixed before it goes to beta right? Can someone confirm whether or not bugs like this are usually fixed?

…for some users, apparently, but not all. Is that right?