wtx - Case 12.2.2 : Pass - 59 ms @ 2023-09-27T21:04:12.840Z

Case Description

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

Case Expectation

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

Case Outcome

Ok, received all echo'ed messages in time.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=321&agent=wtx HTTP/1.1
Connection: Upgrade
Host: 127.0.0.1:9080
Sec-WebSocket-Key: IixxfokHAVUsfT2omVAtow==
Sec-WebSocket-Version: 13
Upgrade: websocket
Sec-Websocket-Extensions: permessage-deflate; client_max_window_bits=12; server_max_window_bits=12; client_no_context_takeover; server_no_context_takeover

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: GTlQK/k66nHsYiyMCxszZPUli+Q=
Sec-WebSocket-Extensions: permessage-deflate; server_no_context_takeover; server_max_window_bits=12

Closing Behavior

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

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
8	1	8
43	1	43
56	2	112
57	1	57
58	14	812
59	3	177
60	10	600
61	5	305
62	4	248
63	8	504
64	4	256
65	8	520
66	1	66
67	6	402
68	3	204
69	6	414
70	12	840
71	11	781
72	356	25632
73	132	9636
74	16	1184
76	397	30172
335	1	335
Total	1002	73308

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
36	1	36
52	2	104
53	1	53
54	12	648
55	3	165
56	9	504
57	6	342
58	4	232
59	9	531
60	5	300
61	5	305
62	3	186
63	5	315
64	4	256
65	7	455
66	12	792
67	42	2814
68	339	23052
69	125	8625
70	18	1260
72	388	27936
307	1	307
Total	1002	69222

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

               6f6e3a20557067726164650d0a48 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

002 WIRELOG DISABLED

003 CLOSE CONNECTION AFTER 60.000000 sec

004 WIRELOG ENABLED

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

               0x03e8

006 TX OCTETS: 880203e8

007 RX OCTETS: 888209322f210ada

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

               0x03e8

009 TCP DROPPED BY ME