-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Issue path validation #534
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
Conversation
I second the importance of this change. |
The old way: If the client connects with a wrong path, the connection will hang. Both the server and the client can know what hanppened. I think the server should tell to the client what happened. |
@@ -2081,7 +2081,11 @@ describe('WebSocket', function() { | |||
}); | |||
ws.on('close', function() { | |||
setTimeout(function() { | |||
assert.ok(errorGiven); | |||
if (errorGiven) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get this change. The assertion is useless now as it's always true.
Can you please add a test for this? Thank you. |
ok |
When a client visits a server with a wrong path, the connection should be rejected.
c2071c9
to
52f0b33
Compare
52f0b33
to
98af262
Compare
@lpinca I have added a test |
@fatelei thank you. LGTM. |
When a client visits a server with a wrong path, the connection should be rejected.