Read in init fails about elephant.io HOT 5 CLOSED

https://tools.ietf.org/html/rfc6455#section-5.2 Readin the RFC and looking at what which bit means tells me the comparison with 0x00 and 0xff is just wrong...

I now know what those first bytes are:

1000 0001 = 0x81
|||| ||||
|||| |||+-\
|||| ||+--> Opcode, in this case, 0x1 means text frame
|||| |+---|
|||| +----/
||||
|||+-\
||+--> Reserved
|+---/
* This is the final frame (first frame can also be final)

00000011 = 3 = payload length (strlen of ::1)

from elephant.io.

Hi @Pitel ,

We do not use in our project the read function.. And we are not yet going to do so.

All I can is calling @ludovicbarreca 's help :)

from elephant.io.

Also, the master implementation was websocket heybi-16 protocol. Is it the one you use?

from elephant.io.

I don't know, I use what Socket.io in node.js is using. And it seems to be the same thing described in RFC.

I am working on a patch, it should be done in couple of hours. :)

from elephant.io.

Thanks for your review. It is now merged.

Best

from elephant.io.