Autobahn WebSocket Testsuite Report
Autobahn WebSocket

gws-server/sync/context_take_over - Case 4.1.2 : Pass - 1 ms @ 2024-01-18T07:31:12.280Z

Case Description

Send frame with reserved non-control Opcode = 4 and non-empty payload.

Case Expectation

The connection is failed immediately.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /connect HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:8000
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: 9cVhXcHMpdVmuJtHKyr9cA==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: KTA/rsIaHNnXMVVlCvo2ylQCiGU=


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).
remoteCloseCode1002The close code the peer sent me in close frame (if any).
remoteCloseReasongws: unexpected opcode 4The close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
28128
1291129
Total2157

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
29129
2471247
Total3284

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
41
81
Total2


Wire Log

000 TX OCTETS: 474554202f636f6e6e65637420485454502f312e310d0a557365722d4167656e743a204175746f6261686e54657374537569
               74652f302e382e322d302e31302e ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=4, FIN=True, RSV=0, PAYLOAD-LEN=23, MASK=73b6bed8, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               reserved opcode payload
003 TX OCTETS: 849773b6bed801d3cdbd01c0dbbc53d9cebb1cd2dbf803d7c7b41cd7da
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 881a03ea6777733a20756e6578706563746564206f70636f64652034
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=26, MASKED=False, MASK=None
               0x03ea6777733a20756e6578706563746564206f70636f64652034
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=951c8955, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
008 TX OCTETS: 8882951c895596f4
009 TCP DROPPED BY PEER