websock server - Case 12.3.3 : Pass - 162 ms @ 2024-11-28T05:33:33.449Z

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 /ws HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:8888
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: c5oSL9YXt9mkoc6xOw5czw==
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits
Sec-WebSocket-Version: 13

HTTP/1.1 101 Switching Protocols
Date: Thu, 28 Nov 2024 05:33:33 GMT
Sec-Websocket-Extensions: permessage-deflate; client_no_context_takeover
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: igZ1pQZZZsJ0+XyAVuXuIkAToQ8=

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
240	1	240
260	1000	260000
Total	1002	260244

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
148	1	148
154	1	154
155	1	155
156	1	156
161	1	161
162	2	324
163	1	163
165	1	165
166	1	166
167	1	167
168	2	336
169	3	507
170	5	850
171	5	855
172	4	688
173	2	346
174	5	870
175	3	525
176	8	1408
177	8	1416
178	6	1068
179	6	1074
180	9	1620
181	8	1448
182	16	2912
183	19	3477
184	17	3128
185	30	5550
186	22	4092
187	32	5984
188	28	5264
189	41	7749
190	30	5700
191	44	8404
192	44	8448
193	50	9650
194	41	7954
195	52	10140
196	48	9408
197	39	7683
198	44	8712
199	48	9552
200	42	8400
201	35	7035
202	36	7272
203	23	4669
204	28	5712
205	15	3075
206	25	5150
207	19	3933
208	11	2288
209	9	1881
210	12	2520
211	5	1055
212	6	1272
213	2	426
219	2	438
340	1	340
Total	1002	194051

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

               382e322d302e31302e390d0a486f ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f

               7620323032342030353a33333a33 ...

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=7ed15ec0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

006 TX OCTETS: 88827ed15ec07d39

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