Autobahn WebSocket Testsuite Report
Autobahn WebSocket

rust-websocket - Case 7.13.2 : Informational - 1 ms @ 2018-10-31T02:17:59.240Z

Case Description

Send close with close code 65536

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.8.0-0.10.9
Host: 127.0.0.1:9002
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: Z7sYg50/0+xRsWuJyhePzQ==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Sec-WebSocket-Accept: HLe8J771K/oTzMDGg806w9SDg6s=
Connection: Upgrade
Upgrade: websocket


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 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.
localCloseCode65535The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCodeNoneThe close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
212
1291129
Total2131

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: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562536f636b65742d4163
               636570743a20484c65384a373731 ...
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=8e85adad, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0xffff
003 TX OCTETS: 88828e85adad717a
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 8800
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
007 TCP DROPPED BY PEER