Websocket Authentication
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I used a web browser inside android app to login to a node.js website, but when I use websocket-sharp, the same server refuses it because it's not authorized.
Obviously, I need to add some kind of session cookies or perhaps andriod id from the webrowser to websocket. I tried researching it on my own with no success. Can anyone offer more information about it?
Thank!
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 issue names websocket-sharp and a Node.js website but no repository files, tests, or entry points. Start by reproducing the browser login and WebSocket connection, then inspect websocket-sharp's authentication-related API and compare it with the server's requirements. Done is undefined until the required authorization flow is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, node.js
- Domain
- authentication, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100