UnknownServer - Case 7.1.6 : Informational - 91 ms @ 2023-03-11T01:20:46.949Z

Case Expectation

Case outcome depends on implementation defined close behavior. Message and close frame are sent back to back. If the close frame is processed before the text message write is complete (as can happen in asynchronous processing models) the close frame is processed first and the text message may not be received or may only be partially recieved.

Case Outcome

Close was processed before text message could be returned.

Expected:
{'NON-STRICT': [], 'OK': [('message', u'Hello World!', False)]}

Observed:
[]

Case Closing Behavior

The spec requires the connection to be failed cleanly here (INFORMATIONAL)

Opening Handshake

Closing Behavior

Wire Statistics

Octets Received by Chop Size

Octets Transmitted by Chop Size

Frames Received by Opcode

Frames Transmitted by Opcode

Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e

               312d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20576562536f636b

               65740d0a436f6e6e656374696f6e ...

002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=10, MASK=18a31656, PAYLOAD-REPEAT-LEN=262144, CHOPSIZE=None, SYNC=False

               BAsd7&jh23

003 TX OCTETS: 81ff000000000004000018a316565ae265322f857c3e2a9054176bc7217072cb24655ae265322f857c3e2a9054176bc72170

               72cb24655ae265322f857c3e2a90 ...

004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=dee68f2c, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               Hello World!

005 TX OCTETS: 818cdee68f2c9683e340b1c6d843ac8aeb0d

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

               0x03e8

007 TX OCTETS: 8882c164497ec28c

008 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=6af6e27c, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

009 TX OCTETS: 89806af6e27c

010 FAIL CONNECTION AFTER 1.000000 sec

011 RX OCTETS: 817f00000000000400004241736437266a6832334241736437266a6832334241736437266a6832334241736437266a683233

               4241736437266a68323342417364 ...

012 RX OCTETS: 6a6832334241736437266a6832334241736437266a6832334241736437266a6832334241736437266a683233424173643726

               6a6832334241736437266a683233 ...

013 TCP DROPPED BY PEER

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	False	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	peer dropped the TCP connection without previous WebSocket closing handshake	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	1000	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	None	The close code the peer sent me in close frame (if any).
remoteCloseReason	None	The close reason the peer sent me in close frame (if any).

Chop Size	Count	Octets
129	1	129
65536	2	131072
Total	3	131201

Chop Size	Count	Octets
6	1	6
8	1	8
18	1	18
240	1	240
262158	1	262158
Total	5	262430