cscheid/R-Websockets — comment on commit 88126254b95e5fd0049f17b6268cab3f9a515476
File:  line 0
By cscheid:

This bug wasn't manifesting itself until now because all messages had FIN=1 and opcode=1, and so the head byte was a bit-palindrome!

However, when I added support for binary messages, the previous code would fail on chrome with a message saying that reserved bits had been set. Looking at page 30 of the protocol spec, here:

http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-17

As changed, the messages will be accepted by Google Chrome 17 with opcode=1L and opcode=2L