Autobahn WebSocket Testsuite Report
Autobahn WebSocket

go-httpbin - Case 2.5 : Pass - 1 ms @ 2025-02-22T12:05:20.396Z

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 / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:43873
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: todL3s3n3NfKiRiTr942Zg==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Connection: upgrade
Sec-Websocket-Accept: sbbq5xb9DJC1bSycb07/YrVuTA0=
Upgrade: websocket
Date: Sat, 22 Feb 2025 12:05:20 GMT


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).
remoteCloseReasoncontrol frame payload exceeds 125 bytesThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
43143
1661166
Total2209

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
1341134
2411241
Total3383

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
91
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2075706772
               6164650d0a5365632d576562736f ...
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=38225805, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
               fefefefefefefefefefefefefefefe ...
003 TX OCTETS: 89fe007e38225805c6dca6fbc6dca6fbc6dca6fbc6dca6fbc6dca6fbc6dca6fbc6dca6fbc6dca6fbc6dca6fbc6dca6fbc6dc
               a6fbc6dca6fbc6dca6fbc6dca6fb ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 882903ea636f6e74726f6c206672616d65207061796c6f6164206578636565647320313235206279746573
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=41, MASKED=False, MASK=None
               0x03ea636f6e74726f6c206672616d65207061796c6f6164206578636565647320313235206279746573
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=767856a6, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
008 TX OCTETS: 8882767856a67590
009 TCP DROPPED BY PEER