Autobahn WebSocket Testsuite Report
Autobahn WebSocket

web-sct 0.2.0 - Case 2.5 : Pass - 11 ms @ 2021-01-18T16:52:42.149Z

Case Description

Send ping with binary payload of 126 octets.

Case Expectation

Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..

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=21&agent=web-sct%200.2.0 HTTP/1.1
Host: localhost:5555
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: Sl/IvP9+W742I2AaI4V37Q==
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: UkgDJkm98QWg+89rH5H4HTzX9bM=


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).
remoteCloseCode1002The close code the peer sent me in close frame (if any).
remoteCloseReasonToo long control frame dataThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
35135
2091209
Total2244

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
1301130
2061206
Total3340

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
91
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3231266167656e743d7765622d736374253230302e322e3020485454502f312e
               310d0a486f73743a206c6f63616c ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
               fefefefefefefefefefefefefefefe ...
003 TX OCTETS: 897e007efefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
               fefefefefefefefefefefefefefe ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 889de2fdfa52e117ae3d8ddd963d8c9ada318d938e208d91da34909c9737c2999b2683
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=29, MASKED=True, MASK=6532666466613532
               0x03ea546f6f206c6f6e6720636f6e74726f6c206672616d652064617461
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
008 TX OCTETS: 880203e8
009 TCP DROPPED BY ME