The routine for encoding of websocket frame sizes larger than 65535 currently encodes them in the machine endianess, instead of big endian as required by the websocket standard.
This leads to disconnects for messages larger than 65535 bytes as they are encoded as being several exabytes in size.
The routine for encoding of websocket frame sizes larger than 65535 currently encodes them in the machine endianess, instead of big endian as required by the websocket standard.
This leads to disconnects for messages larger than 65535 bytes as they are encoded as being several exabytes in size.