wslay - Case 4.1.3 : Non-Strict - 0 ms @ 2012-01-09T14:45:54Z
Case Description
Send small text message, then send frame with reserved non-control Opcode = 5, then send Ping.
Case Expectation
Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.
Case Outcome
Actual events match at least one expected.
Expected:
{'NON-STRICT': [], 'OK': [('message', 'Hello, world!', False)]}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnWebSocketsTestSuite/0.4.10 Host: localhost:9090 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: K0GZDfGX7wNk8KAPygArgw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: zqqtRwezFN2Q5zHuA2iwVA6WphM=
| 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 WebSockets 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. |
| 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 | None | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 129 | 1 | 129 |
| Total | 2 | 133 |
| Chop Size | Count | Octets |
| 6 | 2 | 12 |
| 8 | 1 | 8 |
| 19 | 1 | 19 |
| 201 | 1 | 201 |
| Total | 5 | 240 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 5 | 1 |
| 8 | 1 |
| 9 | 1 |
| Total | 4 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393039300d0a557067726164653a20776562736f
636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a204b30475a
4466475837774e6b384b41507967417267773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a207a7171
745277657a464e3251357a4875413269775641365770684d3d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=5d403616, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818d5d40361615255a7a326c166132325a727c
004 TX FRAME : OPCODE=5, FIN=True, RSV=0, MASK=2ad4c8c3, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
005 TX OCTETS: 85802ad4c8c3
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, MASK=fad873d0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 8980fad873d0
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 880203ea
010 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
ê
011 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=847bb296, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
è
012 TX OCTETS: 8882847bb2968793
013 TCP DROPPED BY PEER