Accessing registered WebSocketBehaviours in HttpServer through Public IP Addresses
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I have been using a HttpServer in my server-side application. The registered WebsocketBehaviours work perfectly when I use '127.0.0.1' or 'localhost' to connect to the server. But when I use the public IP the client is not able to establish a web socket connection with the registered WebsocketBehaviours. It would be great if anyone could help out with this issue.
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 reproducing the connection through the public IP and inspect the HttpServer and registered WebsocketBehaviours setup, comparing it with localhost and 127.0.0.1. Done means identifying the cause of the failed WebSocket connection and documenting a concrete correction; the issue names no file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100