wtx - Case 12.5.2 : Pass - 55 ms @ 2023-09-27T21:06:33.750Z

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=375&agent=wtx HTTP/1.1
Connection: Upgrade
Host: 127.0.0.1:9080
Sec-WebSocket-Key: SGJEEGOr548c6UqyVnmMYg==
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: rWkiD9nhZ2YzG4+B+14XAkjHtbo=
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	2	96
49	2	98
50	2	100
51	3	153
52	3	156
53	3	159
54	1	54
55	1	55
56	3	168
57	8	456
58	7	406
59	3	177
60	3	180
61	1	61
62	2	124
63	1	63
64	1	64
65	1	65
66	2	132
68	4	272
69	1	69
70	5	350
72	7	504
73	10	730
74	4	296
76	920	69920
335	1	335
Total	1002	75251

Octets Transmitted by Chop Size

Chop Size	Count	Octets
4	1	4
39	1	39
40	2	80
42	1	42
43	3	129
44	1	44
45	2	90
46	2	92
47	3	141
49	5	245
50	5	250
51	7	357
52	2	104
53	4	212
54	2	108
55	4	220
57	2	114
59	2	118
61	1	61
63	4	252
64	4	256
65	2	130
66	2	132
67	5	335
68	3	204
69	12	828
70	3	210
72	916	65952
307	1	307
Total	1002	71056

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

               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: 88828533525986db

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

               0x03e8

009 TCP DROPPED BY ME