The length of payload data of a control frame is greater than 125 bytes.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to send data from websocket-sharp to a https://github.com/statianzo/Fleck server and it will not send a large amount of data over websockets. The byte length of the message is close to 16000, so I am not sure if that is absolutely too large or if there is a way to send it in multiple messages.
Also should mention that it seems to send data when it is past 125 bytes normally...I have sent 251 bytes, 300 bytes, 287 bytes
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported behavior with websocket-sharp and a Fleck server using a payload near 16,000 bytes, then compare it with the reported 251-, 300-, and 287-byte cases. Inspect how the WebSocket protocol distinguishes control frames from larger messages. Done means the intended handling of large payloads is established and the behavior is covered by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100