Tungstenite - Case 13.5.5 : Fail - 1 ms @ 2020-09-07T18:52:55.073Z

Case Description

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

Case Expectation

Receive echo'ed messages (with payload as sent). Timeout case after 480 secs.

Case Outcome

Case did not finish within 480 seconds.

Expected:
{}

Observed:
[]

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)

Opening Handshake

GET /runCase?case=468&agent=Tungstenite HTTP/1.1
Host: localhost:9001
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: QBUhySiU6rUOpse5Uld77A==
sec-websocket-extensions: permessage-deflate; client_max_window_bits

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: +w1Yi+SFEhxnF/fCW5F3AudD2p0=
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits=8

Closing Behavior

Key	Value	Description
isServer	True	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	False	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	False	True, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	peer dropped the TCP connection without previous WebSocket closing handshake	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	None	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	None	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
257	1	257
Total	1	257

Octets Transmitted by Chop Size

Chop Size	Count	Octets
306	2	612
Total	2	612

Frames Received by Opcode

Opcode	Count
Total	0

Frames Transmitted by Opcode

Opcode	Count
1	1
Total	1

Wire Log

Wire log after handshake disabled!

000 RX OCTETS: 474554202f72756e436173653f636173653d343638266167656e743d54756e677374656e69746520485454502f312e310d0a

               486f73743a206c6f63616c686f73 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e382e ...

002 WIRELOG DISABLED

003 CLOSE CONNECTION AFTER 480.000000 sec

004 TCP DROPPED BY PEER