Chrome/71.0.3578.98 - Case 9.4.2 : Pass - 1215 ms @ 2019-01-06T16:44:51.813Z
Case Description
Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 256.
Case Expectation
Receive echo'ed binary message (with payload as sent).
Case Outcome
Received binary message of length 4194304.
Expected:
{}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=269&agent=Chrome/71.0.3578.98 HTTP/1.1 Host: 127.0.0.1:9001 Connection: Upgrade Pragma: no-cache Cache-Control: no-cache User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Upgrade: websocket Origin: file:// Sec-WebSocket-Version: 13 Accept-Encoding: gzip, deflate, br Accept-Language: en-US,en;q=0.9,ca;q=0.8,es;q=0.7 Sec-WebSocket-Key: MCw/aAUdIzU9sG8NjiCOrA== Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.8.1-0.10.9 X-Powered-By: AutobahnPython/0.10.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: ARxpbdFPI7SKAqp5J9u67aREXuY=
Key | Value | Description |
isServer | True | 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 | True | 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 |
8 | 1 | 8 |
540 | 1 | 540 |
13888 | 1 | 13888 |
52096 | 1 | 52096 |
65536 | 63 | 4128768 |
Total | 67 | 4195300 |
Chop Size | Count | Octets |
2 | 1 | 2 |
4 | 1 | 4 |
206 | 1 | 206 |
260 | 16384 | 4259840 |
Total | 16387 | 4260052 |
Opcode | Count |
0 | 31 |
2 | 1 |
8 | 1 |
Total | 33 |
Opcode | Count |
0 | 16384 |
2 | 1 |
8 | 1 |
Total | 16386 |
000 RX OCTETS: 474554202f72756e436173653f636173653d323639266167656e743d4368726f6d652f37312e302e333537382e3938204854
54502f312e310d0a486f73743a20 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 CLOSE CONNECTION AFTER 100.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
004 TX OCTETS: 880203e8
005 RX OCTETS: 88825757a61954bf
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3537353761363139
0x03e8
007 TCP DROPPED BY ME