sta / sta/websocket-sharp

The header of a frame cannot be read from the stream ?

Open
#381 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
6.1k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

hi , my problem is when i sent a long String , the error happened
like :|Fatal|<>c__DisplayClass17.<startReceiving>b__16|WebSocketSharp.WebSocketException: The header of a frame cannot be read from the stream. 於 WebSocketSharp.WebSocketFrame.processHeader(Byte[] header) 於 WebSocketSharp.WebSocketFrame.<>c__DisplayClassa.<readHeaderAsync>b__9(Byte[] bytes) 於 WebSocketSharp.Ext.<>c__DisplayClass9.<ReadBytesAsync>b__8(IAsyncResult ar) WebSocketSharp.CloseEventArgs
And i found someone had the problem too
like this
so i wonder know ,how can i solve this problem
and i try to set FragmentLength ,but i don't know how to do that
my Application is a Winsform client include websocketsharp.dll(on Nuget version 1.0.3-rc11)
and i try to sent long String to Stomp&SockJs Websocket Server
BTW,Sending short String is work , and i found the max length i can sent (Encoding.GetEncoding("utf-8").GetBytes ) it's 16546 , Any ideas?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the stack-trace entry points WebSocketFrame.processHeader and readHeaderAsync, then review how the WebSocketSharp client handles the reported UTF-8 payload size near 16546 bytes. Reproduce the failure with short and long strings against the stated STOMP/SockJS server; done means the cause and supported handling of long messages are established.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.