Autobahn WebSocket Testsuite Report
Autobahn WebSocket

WSServer (HTTPS) - Case 7.9.3 : Pass - 2 ms @ 2020-12-10T23:53:55.900Z

Case Description

Send close with invalid close code 1004

Case Expectation

Clean close with protocol error code or drop TCP

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.1-0.10.9
Host: 127.0.0.1:9011
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: HthhTo4deIgpGshtm8dO6w==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Sec-Websocket-Accept: UjgWEeXOGxazbsddx7SQaDHnduI=
Upgrade: websocket
Connection: Upgrade
Server: WSServer/v2.0.7


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.
localCloseCode1004The 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).
remoteCloseReasonExperienced a protocol errorThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
32132
1541154
Total2186

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
               312d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562736f636b65742d4163
               636570743a20556a67574565584f ...
002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=e1d359d1, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03ec
003 TX OCTETS: 8882e1d359d1e23f
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 881e03ea457870657269656e63656420612070726f746f636f6c206572726f72
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=30, MASKED=False, MASK=None
               0x03ea457870657269656e63656420612070726f746f636f6c206572726f72
007 TCP DROPPED BY PEER