Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"code":1,"message":"Session ID unknown" - 400 (Bad Request)
See original GitHub issueI’m running a single Socket.io server ( 2.0.3 ) .
In the client side i’m trying to allow only polling mode.
io.connect(url, {
"transports": ['polling']
})
The problem is that polling fails and throws:
"code":1,"message":"Session ID unknown" response. And the client get disconnected.
i have tried to place node-http-proxy server in front of the socket.io server. So the client connect to node-http-proxy server. This solved the problem, but i don’t understand why…
Can someone please explain why this is happening and how to fix it ???
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I run into this issue as well, my server is executed in docker containers behind a load balancer. I assume this happens because the request polling request do not arrive in the same container everytime.
For future readers: please see the documentation here.