Autobahn WebSocket Testsuite Report
Autobahn WebSocket

bandit - Case 6.4.4 : Non-Strict - 2063 ms @ 2022-09-24T15:58:03.289Z

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

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: host.docker.internal:4000
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: mqc4/nJRVaaBWqRL1P1NDA==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
content-length: 0
cache-control: max-age=0, private, must-revalidate
upgrade: websocket
connection: Upgrade
sec-websocket-accept: km76C0VWo0q1pMG6ojbTdjDKf+k=


Closing Behavior

KeyValueDescription
isServerFalseTrue, 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.
droppedByMeFalseTrue, 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
414
2001200
Total2204

Octets Transmitted by Chop Size

Chop SizeCountOctets
111
6212
8216
12112
2511251
Total7292

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a636f6e74656e742d6c656e6774683a20
               300d0a63616368652d636f6e7472 ...
002 TX OCTETS: 0195c7dec04e
003 TX OCTETS: 096421f37e1143807b1075ba
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: 57
007 DELAY 1.000000 sec for TAG B
008 DELAY TIMEOUT on TAG B
009 TX OCTETS: 5e402ba3b7b42ba3
010 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=7fa28b3a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
011 TX OCTETS: 80807fa28b3a
012 FAIL CONNECTION AFTER 1.000000 sec
013 RX OCTETS: 880203ef
014 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None
               0x03ef
015 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=daac20e1, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
016 TX OCTETS: 8882daac20e1d944
017 TCP DROPPED BY PEER