You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(wstest) luigi@ubuntu:~/test$ uname -a
Linux ubuntu 4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
(wstest) luigi@ubuntu:~/test$ cat fuzzingserver.json
{
"url": "ws://192.168.0.31:9001",
"outdir": "./reports/clients",
"cases": ["*"],
"exclude-cases": [],
"exclude-agent-cases": {}
}
(wstest) luigi@ubuntu:~/test$ wstest -m fuzzingserver
Using implicit spec file 'fuzzingserver.json'
Loading spec from /home/luigi/test/fuzzingserver.json
Using Twisted reactor class <class 'twisted.internet.epollreactor.EPollReactor'>
Using UTF8 Validator class <type 'wsaccel.utf8validator.Utf8Validator'>
Using XOR Masker classes <type 'wsaccel.xormask.XorMaskerNull'>
Autobahn WebSockets 0.7.5/0.10.9 Fuzzing Server (Port 9001)
Ok, will run 519 test cases for any clients connecting
Description
When the client sends a masked close frame, the server abruptly closes the TCP connection.
Reproducible in
version: 0.7.5
Node.js version(s): 4.8.7, 6.12.2, 8.9.3, 9.2.1
OS version(s): Ubuntu 16.04
Steps to reproduce
1. Start the fuzzingserver
2. Run the following Node.js script
Expected result
The connection is closed cleanly.
Actual result
An error is emitted on the socket.
Additional details
The connection is closed cleanly if the client sends an unmasked close frame.
The text was updated successfully, but these errors were encountered: