rust-websocket - Case 5.11 : Pass - 3 ms @ 2018-10-31T02:17:48.657Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in octet-wise chops.
Case Expectation
The connection is failed immediately, since there is no message to continue.
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.0-0.10.9 Host: 127.0.0.1:9002 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: UddTYXJo3jO+VQsDfHmyvg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Sec-WebSocket-Accept: bhUs0nq55dkASHzaHgaFJvD9ZlQ= Connection: Upgrade Upgrade: websocket
| 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 | None | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | None | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 2 | 1 | 2 |
| 129 | 1 | 129 |
| Total | 2 | 131 |
| Chop Size | Count | Octets |
| 1 | 32 | 32 |
| 240 | 1 | 240 |
| Total | 33 | 272 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562536f636b65742d4163
636570743a2062685573306e7135 ...
002 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=f9c0f4a9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
non-continuation payload
003 TX OCTETS: 80
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=2f81d6b2, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 98
007 TX OCTETS: f9
008 TX OCTETS: c0
009 TX OCTETS: f4
010 TX OCTETS: a9
011 TX OCTETS: 97
012 TX OCTETS: af
013 TX OCTETS: 9a
014 TX OCTETS: 84
015 TX OCTETS: 9a
016 TX OCTETS: af
017 TX OCTETS: 9a
018 TX OCTETS: dd
019 TX OCTETS: 90
020 TX OCTETS: ae
021 TX OCTETS: 81
022 TX OCTETS: c8
023 TX OCTETS: 8d
024 TX OCTETS: a9
025 TX OCTETS: 9b
026 TX OCTETS: c7
027 TX OCTETS: d9
028 TX OCTETS: b0
029 TX OCTETS: 95
030 TX OCTETS: d0
031 TX OCTETS: 95
032 TX OCTETS: af
033 TX OCTETS: 95
034 TX OCTETS: cd
035 TX OCTETS: 81
036 TX OCTETS: 8d
037 RX OCTETS: 8800
038 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
039 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=aba65147, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
040 TCP DROPPED BY PEER