WebSocket-Node 1.0.27 - Case 5.18 : Pass - 3 ms @ 2020-08-28T14:51:12.318Z
Case Description
Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.
Case Expectation
The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.
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.1-0.10.9 Host: host.docker.internal:8080 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: 36wmA62hPPopSSgTG6ox+g== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: fL+1dRSOZpyHcYZ88kizXgOFq/c=
| 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 | Illegal frame opcode 0x1 received in middle of fragmented message. | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 70 | 1 | 70 |
| 129 | 1 | 129 |
| Total | 2 | 199 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 15 | 2 | 30 |
| 251 | 1 | 251 |
| Total | 4 | 289 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 2 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
312d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=b92b1c9d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0189b92b1c9ddf597dfad44e72e988
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=b5c0a7b9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 8189b5c0a7b9d3b2c6ded8a5c9cd87
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 884403ea496c6c6567616c206672616d65206f70636f64652030783120726563656976656420696e206d6964646c65206f66
20667261676d656e746564206d65 ...
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=68, MASKED=False, MASK=None
0x03ea496c6c6567616c206672616d65206f70636f64652030783120726563656976656420696e206d6964646c65206f6620
667261676d656e746564206d657373 ...
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=eb0a0473, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 8882eb0a0473e8e2
011 TCP DROPPED BY PEER