SAMD21 / W5100 / Ethernet - Case 6.4.4 : Non-Strict - 2009 ms @ 2020-06-03T17:02:53.655Z

Case Description

Same as Case 6.4.2, but we send message not in 3 frames, but in 3 chops of the same message frame.

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5f4
PART2 = 90
PART3 =

Case Expectation

The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('timeout', 'A')], 'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')]}

Observed:
[('timeout', 'A'), ('timeout', 'B')]

Opening Handshake

Closing Behavior

Wire Statistics

Octets Received by Chop Size

Octets Transmitted by Chop Size

Frames Received by Opcode

Frames Transmitted by Opcode

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               302d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c73

002 RX OCTETS: 0d0a

003 RX OCTETS: 557067726164653a20776562736f636b6574

004 RX OCTETS: 0d0a

005 RX OCTETS: 436f6e6e656374696f6e3a20557067726164650d0a

006 RX OCTETS: 5365632d576562536f636b65742d4163636570743a2042332b5332416f546e7375585673574d3950627550725a654d46673d

007 RX OCTETS: 0d0a0d0a

008 TX OCTETS: 01956275ee2a

009 TX OCTETS: accf0f97dbba6de4debb5bde

010 DELAY 1.000000 sec for TAG A

011 DELAY TIMEOUT on TAG A

012 TX OCTETS: f2

013 DELAY 1.000000 sec for TAG B

014 DELAY TIMEOUT on TAG B

015 TX OCTETS: f56e4f061c9a4f06

016 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=a32e4461, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

017 TX OCTETS: 8080a32e4461

018 FAIL CONNECTION AFTER 1.000000 sec

019 RX OCTETS: 880203ef

020 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None

               0x03ef

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

               0x03e8

022 TX OCTETS: 88825a72792b599a

023 TCP DROPPED BY PEER

Key	Value	Description
isServer	False	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	False	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	1007	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
2	2	4
4	2	8
18	1	18
21	1	21
32	1	32
50	1	50
Total	8	133

Chop Size	Count	Octets
1	1	1
6	2	12
8	2	16
12	1	12
245	1	245
Total	7	286

Opcode	Count
8	1
Total	1

Opcode	Count
0	1
8	1
Total	2