libwebsockets - Case 9.4.2 : Pass - 6368 ms @ 2017-07-28T05:17:46.756Z

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)

Opening Handshake

GET /runCase?case=271&agent=libwebsockets HTTP/1.1
Pragma: no-cache
Cache-Control: no-cache
Host: 127.0.0.1:9001
Origin: http://127.0.0.1:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: 5bMcYWpO2H5KaVVy0j+sTQ==
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.5-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: Qswhrdk2mQeGWD8gUjmhQq/zbGY=

Closing Behavior

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 WebSockets 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).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
361	1	361
528	6465	3413520
1056	12	12672
1320	3	3960
1584	3	4752
2640	1	2640
2904	1	2904
3960	2	7920
4224	1	4224
4488	3	13464
5016	75	376200
5544	1	5544
5808	1	5808
6072	2	12144
6600	1	6600
8712	1	8712
9504	2	19008
10296	2	20592
13464	1	13464
13992	1	13992
18480	1	18480
27192	1	27192
31416	1	31416
50032	1	50032
53528	1	53528
65536	3	196608
Total	6589	4325751

Octets Transmitted by Chop Size

Chop Size	Count	Octets
2	1	2
4	1	4
206	1	206
260	16384	4259840
Total	16387	4260052

Frames Received by Opcode

Opcode	Count
0	16384
2	1
8	1
Total	16386

Frames Transmitted by Opcode

Opcode	Count
0	16384
2	1
8	1
Total	16386

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323731266167656e743d6c6962776562736f636b65747320485454502f312e31

               0d0a507261676d613a206e6f2d63 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

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: 8882f0117f79f3f9

006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6630313137663739

               0x03e8

007 TCP DROPPED BY ME