ruby-2.2.10 - Case 5.2 : Pass - 1 ms @ 2023-09-07T19:57:42.331Z
Case Description
Send Pong fragmented into 2 fragments.
Case Expectation
Connection is failed immediately, since control message MUST NOT be fragmented.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=46&agent=ruby-2.2.10 HTTP/1.1 Host: 0.0.0.0:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: D5McxrR/Fp6fcXXW4SwqmA== Sec-WebSocket-Version: 13 Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.8.2-0.10.9 X-Powered-By: AutobahnPython/0.10.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: ryH8kO/7en01TUF+J60la1S4nV4=
| 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 | True | 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 | 1002 | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | Received fragmented control frame: opcode = 10 | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 54 | 1 | 54 |
| 254 | 1 | 254 |
| Total | 2 | 308 |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 11 | 2 | 22 |
| 206 | 1 | 206 |
| Total | 4 | 232 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 1 |
| 8 | 1 |
| 10 | 1 |
| Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3436266167656e743d727562792d322e322e313020485454502f312e310d0a48
6f73743a20302e302e302e303a39 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=10, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment1
003 TX OCTETS: 0a09667261676d656e7431
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
fragment2
005 TX OCTETS: 8009667261676d656e7432
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 88b0714eaf3072a4fd55122bc646142a8f56032fc85d1420db55156ecc5f1f3add5f1d6ec9421023ca0a5121df531e2aca10
4c6e9e00
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=48, MASKED=True, MASK=3731346561663330
0x03ea526563656976656420667261676d656e74656420636f6e74726f6c206672616d653a206f70636f6465203d203130
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 880203e8
011 TCP DROPPED BY ME