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:
{'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')], 'OK': [('timeout', 'A')]}

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

Opening Handshake

GET /runCase?case=76&agent=libwsc HTTP/1.1 Host:192.168.0.26:9001 Upgrade:websocket Connection:upgrade Sec-WebSocket-Key:dgiT0w1jHWLSkpw8zejeHw== Sec-WebSocket-Version:13 Sec-WebSocket-Extensions:permessage-deflate; client_no_context_takeover; server_no_context_takeover; client_max_window_bits=9 Origin:http://192.168.0.26:9001

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 RX OCTETS: 474554202f72756e436173653f636173653d3736266167656e743d6c696277736320485454502f312e310d0a486f73743a31

               39322e3136382e302e32363a3930 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

002 TX OCTETS: 0115

003 TX OCTETS: cebae1bdb9cf83cebcceb5f4

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX OCTETS: 90

007 DELAY 1.000000 sec for TAG B

008 DELAY TIMEOUT on TAG B

009 TX OCTETS: 8080656469746564

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

011 TX OCTETS: 8000

012 FAIL CONNECTION AFTER 1.000000 sec

013 RX OCTETS: 889fc548c839c6a78157b329a450a1689d6d8365f019ac26e84da030bc19a82dbb4aa42fad889fdc9dc84cdf728122aafca4

               25b8bd9d189ab0f06cb5f3e838b9 ...

014 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=31, MASKED=True, MASK=6335343863383339

               0x03ef496e76616c6964205554462d3820696e2074657874206d657373616765

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

               0x03e8

016 TX OCTETS: 880203e8

017 TCP DROPPED BY ME

Key	Value	Description
isServer	True	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	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	1007	The close code the peer sent me in close frame (if any).
remoteCloseReason	Invalid UTF-8 in text message	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
74	1	74
339	1	339
Total	2	413

Chop Size	Count	Octets
1	1	1
2	2	4
4	1	4
8	1	8
12	1	12
206	1	206
Total	7	235

Opcode	Count
8	1
Total	1

Opcode	Count
0	1
8	1
Total	2