gws-server/sync/context_take_over - Case 3.2 : Pass - 1 ms @ 2024-01-18T07:31:12.266Z
Case Description
Send small text message, then send again with RSV = 2, then send Ping.
Case Expectation
Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': [('message', u'Hello, world!', False)], 'NON-STRICT': []}
Observed:
[('message', u'Hello, world!', False)]
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:8000 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: QmQvJNbXdPR42gK0jvC7sA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: uxHq6Dg5UHcFQQjNgq/N/clyCt0=
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 |
38 | 1 | 38 |
129 | 1 | 129 |
Total | 2 | 167 |
Chop Size | Count | Octets |
6 | 1 | 6 |
8 | 1 | 8 |
19 | 2 | 38 |
247 | 1 | 247 |
Total | 5 | 299 |
Opcode | Count |
1 | 1 |
8 | 1 |
Total | 2 |
Opcode | Count |
1 | 2 |
8 | 1 |
9 | 1 |
Total | 4 |
000 TX OCTETS: 474554202f636f6e6e65637420485454502f312e310d0a557365722d4167656e743a204175746f6261686e54657374537569
74652f302e382e322d302e31302e ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=e54e16ee, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818de54e16eead2b7a828a6236998a3c7a8ac4
004 TX FRAME : OPCODE=1, FIN=True, RSV=2, PAYLOAD-LEN=13, MASK=ed732664, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
005 TX OCTETS: a18ded732664a5164a08825f061382014a00cc
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=8c7b17f5, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 89808c7b17f5
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 810d48656c6c6f2c20776f726c6421881503ea6777733a2070726f746f636f6c206572726f72
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=False, MASK=None
Hello, world!
011 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=21, MASKED=False, MASK=None
0x03ea6777733a2070726f746f636f6c206572726f72
012 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=7af3666f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
013 TX OCTETS: 88827af3666f791b
014 TCP DROPPED BY PEER