gws-server/async/no_context_take_over - Case 2.5 : Pass - 0 ms @ 2024-01-18T07:54:27.765Z
Case Description
Send ping with binary payload of 126 octets.
Case Expectation
Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /connect HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: 127.0.0.1:8003 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: 31Pk4YlgusxwrAC34VpRnw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: 3F2IEiDHQZKsuAVDg2yuS6EhGXM=
Key | Value | Description |
isServer | False | 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 | 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 | gws: protocol error | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
23 | 1 | 23 |
129 | 1 | 129 |
Total | 2 | 152 |
Chop Size | Count | Octets |
8 | 1 | 8 |
134 | 1 | 134 |
247 | 1 | 247 |
Total | 3 | 389 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
8 | 1 |
9 | 1 |
Total | 2 |
000 TX OCTETS: 474554202f636f6e6e65637420485454502f312e310d0a557365722d4167656e743a204175746f6261686e54657374537569
74652f302e382e322d302e31302e ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=aa2318fc, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
fefefefefefefefefefefefefefefe ...
003 TX OCTETS: 89fe007eaa2318fc54dde60254dde60254dde60254dde60254dde60254dde60254dde60254dde60254dde60254dde60254dd
e60254dde60254dde60254dde602 ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 881503ea6777733a2070726f746f636f6c206572726f72
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=21, MASKED=False, MASK=None
0x03ea6777733a2070726f746f636f6c206572726f72
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=50477d9d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
008 TX OCTETS: 888250477d9d53af
009 TCP DROPPED BY PEER