Autobahn WebSockets Testsuite Report
Autobahn WebSockets

ServerFrameworkServer/6.6.5 - Case 7.13.1 : Informational - 0 ms @ 2017-11-02T08:53:31Z

Case Description

Send close with close code 5000

Case Expectation

Actual events are undefined by the spec.

Case Outcome

Actual events are undefined by the spec.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (INFORMATIONAL)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.5.5-0.5.14
Host: localhost:5051
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: xAfzg/+2CsVkq66S4SkV+g==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: gg3mHj9iHexbyQG+IwIBgIPTokk=


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.
localCloseCode5000The 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).
remoteCloseReasonInvalid status code: 5000The close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
30130
1291129
Total2159

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
2401240
Total2248

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=2, MASK=937e13f9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x1388
003 TX OCTETS: 8882937e13f980f6
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 881c03ea496e76616c69642073746174757320636f64653a203530303000
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=28, MASKED=False, MASK=None
               0x03ea496e76616c69642073746174757320636f64653a203530303000
007 TCP DROPPED BY PEER