libwebsockets - Case 9.6.1 : Pass - 13474 ms @ 2017-07-28T05:17:52.723Z

Case Description

Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 64 octets.

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)

Opening Handshake

GET /runCase?case=285&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: n+bRzE52OzAvMV7fEuGwEQ==
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: t3D+VUGW8c/a2qowmLiOTBLfBDw=

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
8	1	8
361	1	361
1032	1024	1056768
Total	1026	1057137

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
10	1	10
64	16384	1048576
206	1	206
Total	16387	1048796

Frames Received by Opcode

Opcode	Count
0	1023
2	1
8	1
Total	1025

Frames Transmitted by Opcode

Opcode	Count
2	1
8	1
Total	2

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323835266167656e743d6c6962776562736f636b65747320485454502f312e31

               0d0a507261676d613a206e6f2d63 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

002 CLOSE CONNECTION AFTER 1000.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: 8882f8fafea0fb12

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

               0x03e8

007 TCP DROPPED BY ME