Comment 1:

See http://en.wikipedia.org/wiki/WebSocket#Browser_support for the implementation status
of the various versions of the protocol.

Comment 2:

Is anybody working on this change? I have some local work with tests passing that I can
submit in a CL if not.

Comment 3:

hibi 07 and 08 are almost identical to RFC6455, the difference being that one uses
"Origin:" and the other uses "Sec-WebSocket-Origin:". As long as the handshake remains
mostly the same, we should support it as far back as possible.
hixie (hibi 00) is completely different and incompatible. The only browser that supports
it is Safari 5 (OS X, iOS 5). I was originally against removing hixie for this reason,
but I have discovered a way to distinguish hixie from hibi/RFC6455 in JavaScript:
if("WebSocket" in window && WebSocket.CLOSED > 2) {
    // hibi-07 to RFC6455
}
The W3C drafts that coincide with the WebSocket protocol drafts show that the "CLOSED"
constant is equal to "2" when hixie was implemented, and "CLOSED" is equal to "3" in
hibi-07 and later. The only overlap is Chrome 13, which should have zero users with the
auto-updating. Given Apple's long release cycle for Safari, testing "CLOSED" seems to be
a good way to avoid using hixie and use a fallback method like long-polling instead.
So it is possible to ignore Safari 5's WebSocket support and pretend like it has none,
without trying the handshake. So I'm all for this change.

Comment 4:

This issue was closed by revision golang/net@38c17ad.

Status changed to Fixed.