sgcWebSockets - Case 13.4.3 : Pass - 911 ms @ 2019-01-06T15:58:14.605Z

Case Description

Send 1000 compressed messages each of payload size 256, auto-fragment to 0 octets. Use permessage-deflate client offers (requestNoContextTakeover, requestMaxWindowBits): [(False, 15)]

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 /runCase?case=448&agent=sgcWebSockets HTTP/1.1

Host: 127.0.0.1:9001

Upgrade: websocket

Connection: Upgrade

Sec-WebSocket-Key: C+I4OO1BnCFEVqxcYVAMkQ==

Origin: 127.0.0.1

Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits

Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols

Server: AutobahnTestSuite/0.8.1-0.10.9

X-Powered-By: AutobahnPython/0.10.9

Upgrade: WebSocket

Connection: Upgrade

Sec-WebSocket-Accept: 8vDUf/tqSs6O1p1aOrcpesedpVk=

Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits=15


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, 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.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1000The close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
818
176102
188144
1912228
20581160
2138798
221002200
23811863
24882112
25982450
26772002
27772079
28742072
29541566
30441320
31411271
32381216
3326858
3420680
3515525
3613468
377259
384152
404160
41282
42142
433129
44288
46146
47294
48148
56156
58158
75175
80180
1561156
2781278
Total100226925

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
1342546
1470980
1542630
161382208
171051785
18991782
191252375
20721440
21761596
22541188
23531219
2438912
2529725
2622572
2710270
284112
295145
30130
31262
32132
33266
34134
36136
37137
39139
41282
43143
61161
66166
1471147
2791279
Total100219503

Frames Received by Opcode

OpcodeCount
11000
81
Total1001

Frames Transmitted by Opcode

OpcodeCount
11000
81
Total1001


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d343438266167656e743d736763576562536f636b65747320485454502f312e31
               0d0a486f73743a203132372e302e ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
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=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
006 TX OCTETS: 880203e8
007 RX OCTETS: 8882b605be8fb5ed
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6236303562653866
               0x03e8
009 TCP DROPPED BY ME