non-tls - Case 6.4.4 : Non-Strict - 2004 ms @ 2021-07-05T07:51:35.561Z

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')]

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: /X4UEvkL6frQY3TZp9rRRw==
Sec-WebSocket-Version: 13

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

Closing Behavior

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	False	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	peer dropped the TCP connection without previous WebSocket closing handshake	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	None	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	None	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
199	1	199
Total	1	199

Octets Transmitted by Chop Size

Chop Size	Count	Octets
1	1	1
6	2	12
8	1	8
12	1	12
252	1	252
Total	6	285

Frames Received by Opcode

Opcode	Count
Total	0

Frames Transmitted by Opcode

Opcode	Count
0	1
Total	1

Wire Log

000 TX OCTETS: 474554202f6563686f2f6d65737361676520485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465

               737453756974652f302e382e322d ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e74656e742d4c656e6774683a20

               300d0a446174653a204d6f6e2c20 ...

002 TX OCTETS: 01955e0587d2

003 TX OCTETS: 90bf666fe7ca041ce2cb3226

004 DELAY 1.000000 sec for TAG A

005 DELAY TIMEOUT on TAG A

006 TX OCTETS: ce

007 DELAY 1.000000 sec for TAG B

008 DELAY TIMEOUT on TAG B

009 TX OCTETS: 8507b73a6cf3b73a

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

011 TX OCTETS: 808014f9ac12

012 FAIL CONNECTION AFTER 1.000000 sec

013 TCP DROPPED BY PEER