tls - Case 13.4.1 : Pass - 1566 ms @ 2021-07-05T09:40:43.667Z
Case Description
Send 1000 compressed messages each of payload size 16, 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 60 secs.
Case Outcome
Ok, received all echo'ed messages in time.
Expected:
{}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /echo/message HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: localhost:9999 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: lY2tJJqlvnXBKMe7liZljA== Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits; server_max_window_bits=15 Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Content-Length: 0 Date: Mon, 05 Jul 2021 09:40:43 GMT Server: nbio Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: paEgfvW93TlCa2r1Ixxg7HuPNBc= Sec-Websocket-Extensions: permessage-deflate; server_no_context_takeover; client_no_context_takeover
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). |
Chop Size | Count | Octets |
4 | 1 | 4 |
18 | 1000 | 18000 |
301 | 1 | 301 |
Total | 1002 | 18305 |
Chop Size | Count | Octets |
8 | 1 | 8 |
16 | 10 | 160 |
17 | 6 | 102 |
18 | 179 | 3222 |
19 | 58 | 1102 |
20 | 52 | 1040 |
21 | 111 | 2331 |
22 | 57 | 1254 |
23 | 96 | 2208 |
24 | 431 | 10344 |
377 | 1 | 377 |
Total | 1002 | 22148 |
Opcode | Count |
1 | 1000 |
8 | 1 |
Total | 1001 |
Opcode | Count |
1 | 1000 |
8 | 1 |
Total | 1001 |
000 TX OCTETS: 474554202f6563686f2f6d65737361676520485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465
737453756974652f302e382e322d ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e74656e742d4c656e6774683a20
300d0a446174653a204d6f6e2c20 ...
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=450092d0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
006 TX OCTETS: 8882450092d046e8
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