Autobahn WebSocket Testsuite Report
Autobahn WebSocket

web-sct 0.2.0 - Case 7.7.7 : Pass - 9 ms @ 2021-01-18T16:52:54.806Z

Case Description

Send close with valid close code 1009

Case Expectation

Clean close with normal or echoed code

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=229&agent=web-sct%200.2.0 HTTP/1.1
Host: localhost:5555
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: cOV7Air5On8H1FFZtRpS5Q==
Sec-WebSocket-Version: 13
Content-Length: 0
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.0-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: 3FFlFzx5yddyLup+0FqD2HoBhhs=


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, 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.
localCloseCode1009The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1009The close code the peer sent me in close frame (if any).
remoteCloseReasonInvalidAccessErrorThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
26126
2101210
Total2236

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
2061206
Total2210

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
Total1


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323239266167656e743d7765622d736374253230302e322e3020485454502f31
               2e310d0a486f73743a206c6f6361 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03f1
003 TX OCTETS: 880203f1
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 8894c6116800c5e0216eb0700469a2500b63a3621b45b4630772
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=20, MASKED=True, MASK=6336313136383030
               0x03f1496e76616c69644163636573734572726f72
007 TCP DROPPED BY ME