WSServer (HTTP) - Case 7.9.3 : Pass - 5 ms @ 2020-12-10T23:39:30.253Z

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:9010
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: FDK6u9Qn5R4jLtRCLQMV4A==
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Sec-Websocket-Accept: 0LN46EhSrIJQQAneSxNCJYySa8g=
Upgrade: websocket
Connection: Upgrade
Server: WSServer/v2.0.7

Closing Behavior

Key	Value	Description
isServer	False	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	True	True, iff I have initiated closing handshake (that is, did send close first).
failedByMe	False	True, 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.
droppedByMe	False	True, iff I dropped the TCP connection.
wasClean	True	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	None	When wasClean == False, the reason what happened.
wasServerConnectionDropTimeout	False	When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeout	False	When performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeout	False	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	1004	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	1002	The close code the peer sent me in close frame (if any).
remoteCloseReason	Experienced a protocol error	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
32	1	32
154	1	154
Total	2	186

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
240	1	240
Total	2	248

Frames Received by Opcode

Opcode	Count
8	1
Total	1

Frames Transmitted by Opcode

Opcode	Count
8	1
Total	1

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               312d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562736f636b65742d4163

               636570743a20304c4e3436456853 ...

002 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=597f16d1, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03ec

003 TX OCTETS: 8882597f16d15a93

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