gws-client/async - Case 7.1.6 : Informational - 4 ms @ 2024-01-18T07:40:46.121Z

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:
{'OK': [('message', u'Hello World!', False)], 'NON-STRICT': []}

Observed:
[]

Opening Handshake

GET /runCase?case=215&agent=gws-client/async HTTP/1.1 Host: 127.0.0.1:9001 User-Agent: Go-http-client/1.1 Connection: Upgrade Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits Sec-Websocket-Key: bLskyTflF/YxA76aUuLeoQ== Sec-Websocket-Version: 13 Upgrade: websocket

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 RX OCTETS: 474554202f72756e436173653f636173653d323135266167656e743d6777732d636c69656e742f6173796e6320485454502f

               312e310d0a486f73743a20313237 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

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

               BAsd7&jh23

003 TX OCTETS: 817f00000000000400004241736437266a6832334241736437266a6832334241736437266a6832334241736437266a683233

               4241736437266a68323342417364 ...

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

               Hello World!

005 TX OCTETS: 810c48656c6c6f20576f726c6421

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

               0x03e8

007 TX OCTETS: 880203e8

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

009 TX OCTETS: 8900

010 FAIL CONNECTION AFTER 1.000000 sec

011 RX OCTETS: 8882c9ea8db0ca02

012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6339656138646230

               0x03e8

013 TCP DROPPED BY ME

Key	Value	Description
isServer	True	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	True	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	1000	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	1000	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
8	1	8
294	1	294
Total	2	302

Chop Size	Count	Octets
2	1	2
4	1	4
14	1	14
206	1	206
262154	1	262154
Total	5	262380