gws-server/sync/context_take_over - Case 12.2.3 : Pass - 150 ms @ 2024-01-18T07:31:50.373Z

Case Description

Send 1000 compressed messages each of payload size 256, auto-fragment to 0 octets. Use default permessage-deflate offer.

Case Expectation

Receive echo'ed messages (with payload as sent). Timeout case after 120 secs.

Case Outcome

Ok, received all echo'ed messages in time.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /connect HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:8000
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: czbMU8hP6GCfQItRRedyCA==
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; server_max_window_bits=12; client_max_window_bits=12
Sec-WebSocket-Accept: Bmp5//Y3FiitVGAhEHiaJvbyHlw=

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	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).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
4	1	4
257	1	257
260	1000	260000
Total	1002	260261

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
190	1	190
209	1	209
211	2	422
233	2	466
234	1	234
235	7	1645
236	5	1180
237	6	1422
238	1	238
239	3	717
240	4	960
241	1	241
242	3	726
243	2	486
244	2	488
245	2	490
246	4	984
247	4	988
248	5	1240
249	5	1245
250	3	750
251	3	753
252	4	1008
253	2	506
254	13	3302
255	8	2040
256	10	2560
257	10	2570
258	6	1548
259	11	2849
260	12	3120
261	12	3132
262	12	3144
263	29	7627
264	19	5016
265	25	6625
266	22	5852
267	33	8811
268	22	5896
270	683	184410
345	1	345
Total	1002	266443

Frames Received by Opcode

Opcode	Count
2	1000
8	1
Total	1001

Frames Transmitted by Opcode

Opcode	Count
2	1000
8	1
Total	1001

Wire Log

000 TX OCTETS: 474554202f636f6e6e65637420485454502f312e310d0a557365722d4167656e743a204175746f6261686e54657374537569

               74652f302e382e322d302e31302e ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b

               65740d0a436f6e6e656374696f6e ...

002 WIRELOG DISABLED

003 CLOSE CONNECTION AFTER 120.000000 sec

004 WIRELOG ENABLED

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

               0x03e8

006 TX OCTETS: 88821ccd833f1f25

007 RX OCTETS: 880203e8

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

               0x03e8

009 TCP DROPPED BY PEER