wtx - Case 12.3.2 : Pass - 67 ms @ 2023-09-27T21:05:10.923Z

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=339&agent=wtx HTTP/1.1
Connection: Upgrade
Host: 127.0.0.1:9080
Sec-WebSocket-Key: ndsq6qqHi6HoRnzV4f5NWA==
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: +t69shlBTIlVW7Dgfv8SNE8mxDw=
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
48	1	48
53	1	53
54	1	54
56	3	168
57	1	57
58	3	174
59	1	59
60	5	300
61	4	244
62	8	496
63	7	441
64	8	512
65	28	1820
66	25	1650
67	68	4556
68	93	6324
69	123	8487
70	193	13510
71	91	6461
72	231	16632
73	105	7665
335	1	335
Total	1002	70054

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
43	1	43
48	1	48
50	1	50
51	3	153
53	4	212
54	2	108
55	5	275
56	4	224
57	6	342
58	13	754
59	10	590
60	21	1260
61	42	2562
62	67	4154
63	89	5607
64	135	8640
65	183	11895
66	205	13530
67	151	10117
68	41	2788
69	16	1104
307	1	307
Total	1002	64767

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

               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: 8882d9cdf343da25

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

               0x03e8

009 TCP DROPPED BY ME