Connection Failed: Invalid Frame Header in Chrome.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
The first message works. (Send or Broadcast) but the second message always closes the connection in chrome with
"WebSocket connection to 'ws://localhost/' failed: Invalid frame header"
Oddly enough, Internet Explorer doesn't do this. (IE works fine)
I switched from C# Fleck to this and wasn't having any issues before. I really liked how this library could handle HTTP and Websockets. Thanks.
EDIT: Thought I should mention I'm using HttpServer and AddWebSocketService
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 with the HttpServer and AddWebSocketService paths mentioned in the report, then reproduce the second-message failure in Chrome while comparing the behavior with Internet Explorer. Trace the WebSocket frame handling and determine why Chrome receives an invalid frame header; done means repeated messages keep the connection open without breaking existing HTTP and WebSocket 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