Closing on the client generates an error
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
When I attempt to call "Close" on a websocket instance, I always get the exception thrown from here (using within Xamarin / Mono). If I don't call Close, eventually a stream with two bytes (both zeros) arrives which generates this same error. Any thoughts?
private static WebSocketFrame processHeader (byte[] header)
{
if (header.Length != 2)
throw new WebSocketException ("The header of a frame cannot be read from the stream.");
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 failure with Xamarin or Mono and trace the call to processHeader(byte[] header), especially when closing the WebSocket or receiving the reported two zero bytes. Done means the Close call no longer raises this exception and the reported stream condition has a defined, passing behavior.
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