websock secure server - Case 9.2.5 : Pass - 314 ms @ 2024-11-28T05:30:48.375Z
Case Description
Send binary message message with payload of length 8 * 2**20 (16M).
Case Expectation
Receive echo'ed binary message (with payload as sent).
Case Outcome
Received binary message of length 8388608.
Expected:
{}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /wss HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:8889 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: TYbHXrvC8Fu1OKUZCmaG3g== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Date: Thu, 28 Nov 2024 05:30:48 GMT Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: vridas/iYI+iwHrkcTtQwpX5Azo=
| Key | Value | Description |
| isServer | False | True, iff I (the fuzzer) am a server, and the peer is a client. |
| closedByMe | True | 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 | 1000 | 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 |
| 4 | 1 | 4 |
| 10 | 8 | 80 |
| 166 | 1 | 166 |
| 16384 | 512 | 8388608 |
| Total | 522 | 8388858 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 243 | 1 | 243 |
| 8388622 | 1 | 8388622 |
| Total | 3 | 8388873 |
| Opcode | Count |
| 0 | 7 |
| 2 | 1 |
| 8 | 1 |
| Total | 9 |
| Opcode | Count |
| 2 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f30
2e382e322d302e31302e390d0a48 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f
7620323032342030353a33303a34 ...
002 CLOSE CONNECTION AFTER 100.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=d71ec38d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
004 TX OCTETS: 8882d71ec38dd4f6
005 RX OCTETS: 880203e8
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None
0x03e8
007 TCP DROPPED BY PEER