gws-server/async/context_take_over - Case 7.1.6 : Informational - 4 ms @ 2024-01-18T07:38:41.963Z

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 /connect HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:8001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: iW5oR60YrCfX2S2hqJK0xQ== Sec-WebSocket-Version: 13

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: 474554202f636f6e6e65637420485454502f312e310d0a557365722d4167656e743a204175746f6261686e54657374537569

               74652f302e382e322d302e31302e ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b

               65740d0a436f6e6e656374696f6e ...

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

               BAsd7&jh23

003 TX OCTETS: 81ff00000000000400002e7035d96c3146bd19565fb11c4377985d1402ff441807ea6c3146bd19565fb11c4377985d1402ff

               441807ea6c3146bd19565fb11c43 ...

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

               Hello World!

005 TX OCTETS: 818c27a79fd46fc2f3b84887c8bb55cbfbf5

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

               0x03e8

007 TX OCTETS: 8882570b1fa254e3

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

009 TX OCTETS: 8980d884ec01

010 FAIL CONNECTION AFTER 1.000000 sec

011 RX OCTETS: 880203e8

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

               0x03e8

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	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
4	1	4
129	1	129
Total	2	133

Chop Size	Count	Octets
6	1	6
8	1	8
18	1	18
247	1	247
262158	1	262158
Total	5	262437