websocket-driver node-v16 - Case 2.5 : Pass - 1 ms @ 2023-09-07T20:31:55.496Z
Case Description
Send ping with binary payload of 126 octets.
Case Expectation
Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:4007 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: 4KbVrvvGXLN6xDGFqCaajw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: /va1R0BCJI71Lbk/FxpYEKrbp60=
| Key | Value | Description |
| isServer | False | True, iff I (the fuzzer) am a server, and the peer is a client. |
| closedByMe | False | True, iff I have initiated closing handshake (that is, did send close first). |
| failedByMe | False | True, 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. |
| droppedByMe | False | True, iff I dropped the TCP connection. |
| wasClean | True | True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
| wasNotCleanReason | None | When wasClean == False, the reason what happened. |
| wasServerConnectionDropTimeout | False | When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True. |
| wasOpenHandshakeTimeout | False | When performing the opening handshake, but the peer did not finish in time, this gets True. |
| wasCloseHandshakeTimeout | False | When we initiated a closing handshake, but the peer did not respond in time, this gets True. |
| localCloseCode | 1000 | The close code I sent in close frame (if any). |
| localCloseReason | None | The close reason I sent in close frame (if any). |
| remoteCloseCode | 1002 | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | Received control frame having too long payload: 126 | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 55 | 1 | 55 |
| 129 | 1 | 129 |
| Total | 2 | 184 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 134 | 1 | 134 |
| 240 | 1 | 240 |
| Total | 3 | 382 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 8 | 1 |
| 9 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=899b68b3, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
fefefefefefefefefefefefefefefe ...
003 TX OCTETS: 89fe007e899b68b37765964d7765964d7765964d7765964d7765964d7765964d7765964d7765964d7765964d7765964d7765
964d7765964d7765964d7765964d ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 883503ea526563656976656420636f6e74726f6c206672616d6520686176696e6720746f6f206c6f6e67207061796c6f6164
3a20313236
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=53, MASKED=False, MASK=None
0x03ea526563656976656420636f6e74726f6c206672616d6520686176696e6720746f6f206c6f6e67207061796c6f61643a
20313236
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=cc7ec566, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
008 TX OCTETS: 8882cc7ec566cf96
009 TCP DROPPED BY PEER