https://github.com/kelnos/socketioxide-binary-test
repro case for strange binary event behavior using a v4 client
https://github.com/kelnos/socketioxide-binary-test
Last synced: 3 months ago
JSON representation
repro case for strange binary event behavior using a v4 client
- Host: GitHub
- URL: https://github.com/kelnos/socketioxide-binary-test
- Owner: kelnos
- Created: 2024-03-01T07:30:25.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-04-05T15:08:35.000Z (about 1 year ago)
- Last Synced: 2025-01-23T01:10:03.469Z (5 months ago)
- Language: Java
- Size: 29.3 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# socketioxide v4 binary bug reproducer
This reproduces an issue where socketioxide, when acting as a v4 server,
fails to receive binary events properly. The `Vec` passed to the
handler contains the correct binary data, but it is prefixed with a
`0x4` byte.
## To demonstrate
0. Prerequisites:
* A cargo/rust compiler environment
* JDK 11 or greater, and maven
1. In one terminal, run `make run-server`
2. In another terminal, run `make run-client`
3. Assuming both have compiled and run successfully, switch back to the
first terminal and watch for output.
## What actually happens
We see:
```
Got binary data: [4, 98, 105, 110, 97, 114, 121]
```
## What's expected
But we *should* see:
```
Got binary data: [98, 105, 110, 97, 114, 121]
```
## Notes
When socketioxide acts as a v5 server (change the version of the Java
socketio client in `client/pom.xml` to 2.1.0), socketioxide receives
binary frames as expected.
If the client connects using the HTTP polling transport, the issue does
not occur. (Open `Main.java` and change the `options.transports` line
so it only contains `Polling.NAME` to see this in action.)
Other server implementations, such as the
[socket.io-server-java](https://github.com/codeminders/socket.io-server-java)
and [JS socket.io
2.5.0](https://www.npmjs.com/package/socket.io/v/2.5.0) see the binary
frames properly.