-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Failing test connecting to non-default namespace #1681
Comments
That first |
With 0.9.17 works...(with set authorization instead of use of course) |
Good point… Since now |
What I'm trying to do actually is to allow a client only to connect to specific (dynamic) namespaces and reject the connection to other namespaces (thus checking namespace in the first use callback and reject with an Error if namespace doesn't match) |
@fdellabetta for getting the namespace, try |
I have already tried, but seems that socket.nsp.name returns always '/' in On Thu, Jul 17, 2014 at 4:29 AM, Evan Lucas notifications@github.com
|
Have you tried |
No, but that's not what I wanted to do... On Thu, Jul 17, 2014 at 10:24 AM, Evan Lucas notifications@github.com
|
@guille, @evanlucas For my and @smaffer understanding, when a client connect to a namespace, if the namespace does't exist on server, it's automatically created. What about checking something like if (!this.server.nsps[name]) {
debug('namespace %s does not exist', name);
//send error
//close connection
return;
} before line var nsp = this.server.of(name); of |
still the issue exists. |
It seems like there is general agreement for
Closing. |
Test is failing with Error: timeout of 2000ms exceeded
Ubuntu 14.04 x64, node.js 0.10.29, socket.io 1.0.6
The text was updated successfully, but these errors were encountered: