Autobahn WebSockets Testsuite Report
Autobahn WebSockets

ServerFrameworkServer/6.9 - Case 7.3.6 : Pass - 0 ms @ 2017-11-02T08:51:04Z

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 / HTTP/1.1
User-Agent: AutobahnTestSuite/0.5.5-0.5.14
Host: localhost:5050
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: VC7YEESjDtbNuOyQHVRI3w==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: 1uChKeg8GHIo4f+OTutaihlFYAk=


Closing Behavior

KeyValueDescription
isServerFalseTrue, 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.
droppedByMeFalseTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSockets 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).
remoteCloseReasonControl frame is too long at: 126 bytes, max is: 125The close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
57157
1291129
Total2186

Octets Transmitted by Chop Size

Chop SizeCountOctets
1341134
2401240
Total2374

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
Total1


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
               352d302e352e31340d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=f0b27925, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e82a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a
               2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a ...
003 TX OCTETS: 88fe007ef0b27925f35a530fda98530fda98530fda98530fda98530fda98530fda98530fda98530fda98530fda98530fda98
               530fda98530fda98530fda98530f ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 883703ea436f6e74726f6c206672616d6520697320746f6f206c6f6e672061743a203132362062797465732c206d61782069
               733a2031323500
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=55, MASKED=False, MASK=None
               0x03ea436f6e74726f6c206672616d6520697320746f6f206c6f6e672061743a203132362062797465732c206d6178206973
               3a2031323500
007 TCP DROPPED BY PEER