websock secure server - Case 12.2.1 : Pass - 191 ms @ 2024-04-24T05:21:50.636Z
Case Description
Send 1000 compressed messages each of payload size 16, 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)
GET /wss HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:8889 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: Y6WE2II6YDwvZI59IC8duw== Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; client_max_window_bits Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Date: Wed, 24 Apr 2024 05:21:50 GMT Sec-Websocket-Extensions: permessage-deflate; client_no_context_takeover Upgrade: websocket Connection: Upgrade Sec-Websocket-Accept: B4no9cYCeLTSzVzKkkaEpKc17IQ=
| 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 |
| 240 | 1 | 240 |
| Total | 1002 | 18244 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 17 | 1 | 17 |
| 18 | 1 | 18 |
| 19 | 1 | 19 |
| 20 | 1 | 20 |
| 23 | 12 | 276 |
| 24 | 642 | 15408 |
| 25 | 147 | 3675 |
| 26 | 51 | 1326 |
| 28 | 144 | 4032 |
| 341 | 1 | 341 |
| Total | 1002 | 25140 |
| Opcode | Count |
| 2 | 1000 |
| 8 | 1 |
| Total | 1001 |
| Opcode | Count |
| 2 | 1000 |
| 8 | 1 |
| Total | 1001 |
000 TX OCTETS: 474554202f77737320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f30
2e382e322d302e31302e390d0a48 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205765642c203234204170
7220323032342030353a32313a35 ...
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=3c296d3e, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
006 TX OCTETS: 88823c296d3e3fc1
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