Boost.Beast/189-Sync - Case 9.2.3 : Pass - 17 ms @ 2018-11-09T16:24:36.094Z
Case Description
Send binary message message with payload of length 1 * 2**20 (1M).
Case Expectation
Receive echo'ed binary message (with payload as sent).
Case Outcome
Received binary message of length 1048576.
Expected:
{}
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:8080 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: VYXtE1/CPfdG64EFCGp3Aw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: upgrade Sec-WebSocket-Accept: XTHRtrnnziUwu2zUaiuCdzJb0cw= Server: Boost.Beast/189-Sync
| 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 |
| 159 | 1 | 159 |
| 2756 | 1 | 2756 |
| 2766 | 1 | 2766 |
| 10220 | 1 | 10220 |
| 14600 | 1 | 14600 |
| 16224 | 1 | 16224 |
| 18816 | 2 | 37632 |
| 34876 | 1 | 34876 |
| 40880 | 1 | 40880 |
| 41356 | 1 | 41356 |
| 42340 | 1 | 42340 |
| 43800 | 2 | 87600 |
| 46720 | 2 | 93440 |
| 51100 | 1 | 51100 |
| 54020 | 1 | 54020 |
| 62780 | 2 | 125560 |
| 65536 | 6 | 393216 |
| Total | 27 | 1048749 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 240 | 1 | 240 |
| 1048590 | 1 | 1048590 |
| Total | 3 | 1048838 |
| Opcode | Count |
| 2 | 1 |
| 8 | 1 |
| Total | 2 |
| Opcode | Count |
| 2 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 CLOSE CONNECTION AFTER 10.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=031dd1c0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
004 TX OCTETS: 8882031dd1c000f5
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