Autobahn WebSocket Testsuite Report
Autobahn WebSocket

jruby-9.3.10.0 (2.6.8) - Case 7.3.6 : Pass - 5 ms @ 2023-09-07T19:55:17.168Z

Case Description

Send a close frame with close code and close reason which is too long (124) - total frame payload 126 octets

Case Expectation

Clean close with protocol error code or dropped TCP connection.

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=221&agent=jruby-9.3.10.0+%282.6.8%29 HTTP/1.1
Host: 0.0.0.0:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: uA4EJLq861uQXCmlJfzgaA==
Sec-WebSocket-Version: 13
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: xRwtrmjctjuO4EzaSnaN7Klif34=


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.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReason****************************************************************************************************************************The close reason I sent in close frame (if any).
remoteCloseCode1002The close code the peer sent me in close frame (if any).
remoteCloseReasonReceived control frame having too long payload: 126The close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
59159
2701270
Total2329

Octets Transmitted by Chop Size

Chop SizeCountOctets
1301130
2061206
Total2336

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
Total1


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323231266167656e743d6a727562792d392e332e31302e302b253238322e362e
               3825323920485454502f312e310d ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e82a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a
               2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a ...
003 TX OCTETS: 887e007e03e82a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a
               2a2a2a2a2a2a2a2a2a2a2a2a2a2a ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 88b516bf36b0155564d575da5fc673db16d379d142c279d316d664de5bd536d757c67fd1519062d059907ad058d736cf57c9
               7ad057d42c9f078220
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=53, MASKED=True, MASK=3136626633366230
               0x03ea526563656976656420636f6e74726f6c206672616d6520686176696e6720746f6f206c6f6e67207061796c6f61643a
               20313236
007 TCP DROPPED BY ME