non-tls - Case 9.3.4 : Pass - 1232 ms @ 2021-07-05T07:51:54.995Z

Case Description

Send fragmented text message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 4k.

Case Expectation

Receive echo'ed text message (with payload as sent).

Case Outcome

Received text message of length 4194304.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /echo/message HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: localhost:9998
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: FJgZvTQVnWWBuM+gqIJMPw==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Content-Length: 0
Date: Mon, 05 Jul 2021 07:51:54 GMT
Sec-Websocket-Accept: V+iQkDdr7dj7B/zObzUxXSM96wY=
Server: nbio
Upgrade: websocket
Connection: Upgrade

Closing Behavior

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

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
4	1	4
199	1	199
28632	1	28632
41000	1	41000
65536	63	4128768
Total	67	4198603

Octets Transmitted by Chop Size

Chop Size	Count	Octets
6	1	6
8	1	8
252	1	252
4104	1024	4202496
Total	1027	4202762

Frames Received by Opcode

Opcode	Count
0	1023
1	1
8	1
Total	1025

Frames Transmitted by Opcode

Opcode	Count
0	1024
1	1
8	1
Total	1026

Wire Log

000 TX OCTETS: 474554202f6563686f2f6d65737361676520485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465

               737453756974652f302e382e322d ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e74656e742d4c656e6774683a20

               300d0a446174653a204d6f6e2c20 ...

002 CLOSE CONNECTION AFTER 100.000000 sec

003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=f5b38749, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

004 TX OCTETS: 8882f5b38749f65b

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