Error codes returned when an Upgrade request is denied is not reported back to caller
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
When a websocket connection is being created and an HTTP Upgrade request is sent, if the server returns an HTTP response back with an error code (such as 403 Forbidden, 503 Service Unavailable), this error code is not propagated back to the caller in the OnError event. The caller has no way to figure out why the connection attempt failed.
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
The payload names no files or tests; begin at WebSocket connection setup and HTTP Upgrade response handling, then trace how failures reach OnError. Confirm the behavior for denied responses such as 403 and 503, and verify that the caller receives the response error code.
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
- Mostly clear
- Newbie friendliness
- 35/100