How to prevent websocket from truncating messages on encountering 0-byte?

[DaveTJones]

I'm trying to set up a server-client pair for a novel cryptographic key generation protocol I'm working with, using a uWebSockets server and WASM client. Everything works well, barring instances where the char I'm sending contains a 0. In these cases the 0 is interpreted as a terminating null-byte and the remainder of the message does not send. Is there any way to escape these 0's, or to set the length of the message ahead of sending such that the whole message is sent independant of its contents?

[hakoptak]

Hi Dave, you are sending data as text. If you send your data in the binary format then it should work fine. You define the data type when setting up your Websocket.

[uNetworkingAB]

A websocket can send (at any time, regardless of set up), messages as binary or text. Binary does not care about the content while text must be utf8 text. This is an argument to ws.send

[uNetworkingAB]

You define the data type when setting up your Websocket.

This is not correct. There is no set up. You can send either, at any point regardless of set up.

[hakoptak]

Ah, my bad. Sorry for the confusion.