Boost.Beast/189-Async - Case 12.5.2 : Pass - 176 ms @ 2018-11-09T16:41:28.779Z

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 / HTTP/1.1

User-Agent: AutobahnTestSuite/0.8.0-0.10.9

Host: 127.0.0.1:8081

Upgrade: WebSocket

Connection: Upgrade

Pragma: no-cache

Cache-Control: no-cache

Sec-WebSocket-Key: 7w+jnI1TOcOxjX4SSBL2NA==

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-Accept: I0LPNNEPtKgVAeXEITIrFOVVpy8=

Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover

Server: Boost.Beast/189-Async

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
39	1	39
43	1	43
44	2	88
45	4	180
46	3	138
47	4	188
49	3	147
50	7	350
51	3	153
52	6	312
53	4	212
54	1	54
55	5	275
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
234	1	234
Total	1002	71009

Octets Transmitted by Chop Size

Chop Size	Count	Octets
8	1	8
43	1	43
44	2	88
46	1	46
47	3	141
48	1	48
49	2	98
50	2	100
51	3	153
53	5	265
54	5	270
55	7	385
56	2	112
57	4	228
58	2	116
59	4	236
61	2	122
63	2	126
65	1	65
67	4	268
68	4	272
69	2	138
70	2	140
71	5	355
72	3	216
73	12	876
74	3	222
76	916	69616
338	1	338
Total	1002	75091

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

               302d302e31302e390d0a486f7374 ...

001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b

               65740d0a436f6e6e656374696f6e ...

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

               0x03e8

006 TX OCTETS: 88826c65fd6e6f8d

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