Autobahn WebSocket Testsuite Report
Autobahn WebSocket

Mint - Case 6.4.3 : Non-Strict - 2006 ms @ 2021-10-12T21:12:45.020Z

Case Description

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

MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564

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

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=76&agent=Mint HTTP/1.1
host: localhost:9001
user-agent: mint/1.3.0
upgrade: websocket
connection: upgrade
sec-websocket-version: 13
sec-websocket-key: hziVBA/0R8sP+JTt8kEt/w==
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: ITtIYpUC02PLWRMA53qavQiy/k8=


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeFalseTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, 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.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1007The close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
818
2031203
Total2211

Octets Transmitted by Chop Size

Chop SizeCountOctets
224
428
616
11111
2061206
Total7235

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
81
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3736266167656e743d4d696e7420485454502f312e310d0a686f73743a206c6f
               63616c686f73743a393030310d0a ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX OCTETS: 0115
003 TX OCTETS: cebae1bdb9cf83cebcceb5
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: f4908080
007 DELAY 1.000000 sec for TAG B
008 DELAY TIMEOUT on TAG B
009 TX OCTETS: 656469746564
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: 888255512a8d56be
014 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3535353132613864
               0x03ef
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