The header of frame cannot be read from the stream
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
2016-01-21 21:34:01|Fatal|<>c__DisplayClass2c.b__2b:1601|WebSock
etSharp.WebSocketException: The header of a frame cannot be read from the stream
.
at WebSocketSharp.WebSocketFrame.processHeader(Byte
[] header) in C:\User\Promises\Desktop\websocket-sharp-master\websocket-sharp\WebSocketFrame.cs:line
429
at WebSocketSharp.WebSocketFrame.<>c__DisplayClassa
.b__9(Byte[] bytes) in C:\User\Promises\Desktop\websocket-sharp-master\websocket-sh
arp\WebSocketFrame.cs:line 529
at WebSocketSharp.Ext.<>c__DisplayClass9.b__8(IAsyncResult ar) in C:\User\Promises\Desktop\websocket-sharp-master\websocket-sharp\Ext.cs:line 651
Client Disconnected [An exception has occurred while receiving.]
Chrome: Worked
Firefox 39: not working
i saw some resolutions in the issue's and i added "this.IgnoreExtensions = true;" to OnOpen but i didnt work.
Server: Windows 7
Client: Windows 7 & Windows XP
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
Start by reviewing WebSocketFrame.cs at processHeader and readHeaderAsync, then follow Ext.cs at ReadBytesAsync to understand the reported receive failure. Reproduce the case with Firefox 39 on the listed Windows clients and compare it with Chrome; done means the frame header is read successfully and the client remains connected.
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
- 25/100