AVR / W5100 / Ethernet - Case 4.1.3 : Non-Strict - 6 ms @ 2020-07-05T17:33:35.119Z
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:
{'OK': [('message', u'Hello, world!', False)], 'NON-STRICT': []}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.0-0.10.9 Host: 192.168.0.101:8089 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: MbrQ4kkNBLK2G46uwW0BHw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Web Socket Protocol Handshake Server: syWebsocket Server X-Powered-By: syWebSocket Server Connection: Upgrade Sec-WebSocket-Accept: +iPaWkCqk2+HsXS7ld+2nK2kqkQ= Upgrade: websocket
| 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 | None | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 201 | 1 | 201 |
| Total | 2 | 205 |
| Chop Size | Count | Octets |
| 6 | 2 | 12 |
| 8 | 1 | 8 |
| 19 | 1 | 19 |
| 244 | 1 | 244 |
| Total | 5 | 283 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 5 | 1 |
| 8 | 1 |
| 9 | 1 |
| Total | 4 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e31203130312057656220536f636b65742050726f746f636f6c2048616e647368616b650d0a536572766572
3a207379576562736f636b657420 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=af292124, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello, world!
003 TX OCTETS: 818daf292124e74c4d48c0050153c05b4d408e
004 TX FRAME : OPCODE=5, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=393f4327, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
005 TX OCTETS: 8580393f4327
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=64200331, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 898064200331
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 880203ea
010 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None
0x03ea
011 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=3631e614, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
012 TX OCTETS: 88823631e61435d9
013 TCP DROPPED BY PEER