SocketCluster / SocketCluster/socketcluster
BadConnectionError - socketcluster-client when requesting from server side. It works fine if the request is issued from the browser.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
I have a service that attempts to create a lock on an object and then perform some operations. The process works completely fine when the request is issued from the browser but when trying to do it via server it is failing.
The error that I can see is "BadConnectionError"
socketcluster-client: 16.0.4
socketcluster-server: 16.1.0
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 server-side request with socketcluster-client 16.0.4 and socketcluster-server 16.1.0, then compare it with the working browser request. The issue is done when the server-side lock and subsequent operations complete without BadConnectionError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100