-
-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
namespace is mixed up with query parameters #124
Comments
I can't reproduce this problem here. I just added Can you provide a complete example that reproduces the problem you are seeing, which includes both server and client code? |
it's my mistake that I forgot mention about test environment, here is my setup:
And I'm using the This bug was introduced after socket-io.js@1.4.8, and it's still not fixed. Well, in fact, if you are using socketio-server and socketio-client together, it works fine because socketio-server reuse the code of socketio-client and the server urlparse the namespace. here is my code:
visit: http://localhost:8001 I set a breakpoint in function on_connect, and it's not working. If you could print log or set a breakpoint in method |
Yup, I'm having the same issue with |
@TheJKFever do you have code I can test here? |
I've got my server running on localhost:5000 with a On the client, this works for me:
This does not:
I'm using socketio 2.0.3 from |
By the way, this was not resolved. I can reliably reproduce this issue. With query parameters, the socket will not connect on a namespace. The way I got around this was by not using namespacing at all, and just changing my endpoints to have the namespace in it like |
@TheJKFever This should be resolved now. I put in a fix yesterday. |
I run an AsyncServer example with javascript client socket.io . But it will fail when client connect with query:
And server decode namespace as:
it seems like a bug of socket.io that encoded namesapce with query parameters; I wonder if I can push a compatible pr for this.
The text was updated successfully, but these errors were encountered: