Autobahn WebSocket Testsuite Report
Autobahn WebSocket

node-v20.6.0 - Case 5.1 : Pass - 0 ms @ 2023-09-07T20:12:40.513Z

Case Description

Send Ping fragmented into 2 fragments.

Case Expectation

Connection is failed immediately, since control message MUST NOT be fragmented.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=45&agent=node-v20.6.0 HTTP/1.1
Host: 0.0.0.0:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: Q/CbsC8BJ9OX1tqFWfm0Bg==
Sec-WebSocket-Version: 13
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: gK8vMhyqh7i/2Robo1V3xM7sE1I=


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeFalseTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, iff I have failed the WS connection (i.e. due to protocol error). Failing can be either by initiating closing handshake or brutal drop TCP.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1002The close code the peer sent me in close frame (if any).
remoteCloseReasonReceived fragmented control frame: opcode = 9The close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
53153
2551255
Total2308

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
11222
2061206
Total4232

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
81
91
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3435266167656e743d6e6f64652d7632302e362e3020485454502f312e310d0a
               486f73743a20302e302e302e303a ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=9, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment1
003 TX OCTETS: 0909667261676d656e7431
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment2
005 TX OCTETS: 8009667261676d656e7432
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 88af888277da8b6825bfebe71eacede657bcfae310b7edec03bfeca214b5e6f605b5e4a211a8e9ef12e0a8ed07b9e7e612fa
               b5a24e
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=47, MASKED=True, MASK=3838383237376461
               0x03ea526563656976656420667261676d656e74656420636f6e74726f6c206672616d653a206f70636f6465203d2039
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 880203e8
011 TCP DROPPED BY ME