You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the sync client of websockets-rs to connect to a server written in actix-web over localhost. I've got a 181KB chunk of binary that I'm requesting from my server, then sending back. I'm getting the chunk just fine from the server, but when I try to send it back the server never registers a message. Looking at wireshark, there's some packets that have 0 length. I'm sending the data like this: let bin_message = OwnedMessage::Binary(data); client.send_message(&bin_message)
where data is a Vec<u8>.
A binary chunk of 1264 bytes went back and forth just fine. Do I need to handle the byte streaming myself? Why does this work on the receiving end and not the sending? I've verified my server with a python websocket client, I know it's working on that end.
.pcap of the traffic is attached. dumpfile.zip
The text was updated successfully, but these errors were encountered:
I'm using the sync client of websockets-rs to connect to a server written in actix-web over localhost. I've got a 181KB chunk of binary that I'm requesting from my server, then sending back. I'm getting the chunk just fine from the server, but when I try to send it back the server never registers a message. Looking at wireshark, there's some packets that have 0 length. I'm sending the data like this:
let bin_message = OwnedMessage::Binary(data); client.send_message(&bin_message)
where data is a
Vec<u8>
.A binary chunk of 1264 bytes went back and forth just fine. Do I need to handle the byte streaming myself? Why does this work on the receiving end and not the sending? I've verified my server with a python websocket client, I know it's working on that end.
.pcap of the traffic is attached.
dumpfile.zip
The text was updated successfully, but these errors were encountered: