yawl - Case 6.20.7 : Fail - 39 ms @ 2014-11-25T21:30:16.247Z
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedbfbf
Case Expectation
The connection is failed immediately, since the payload is not valid UTF-8.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
Case Closing Behavior
The connection was failed by the wrong endpoint (FAILED)
GET /runCase?case=160&agent=yawl HTTP/1.1 Connection: keep-alive, Upgrade Pragma: no-cache Cache-Control: no-cache Upgrade: websocket Sec-WebSocket-Version: 13 Sec-WebSocket-Key: SztyeSRDvTV3hdIDt3GGmg== Host: localhost:9001
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.7.1-0.9.3-3 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: B/zZ13Vc+YN1b7+Q2itPJ4jOkb4=
| Key | Value | Description |
| isServer | True | True, iff I (the fuzzer) am a server, and the peer is a client. |
| closedByMe | True | True, iff I have initiated closing handshake (that is, did send close first). |
| failedByMe | True | 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 | False | 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. |
| 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 | 1007 | The close code I sent in close frame (if any). |
| localCloseReason | encountered invalid UTF-8 while processing text message at payload octet index 1 | The close reason I sent in close frame (if any). |
| remoteCloseCode | None | 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 |
| 3 | 1 | 3 |
| 6 | 1 | 6 |
| 235 | 1 | 235 |
| Total | 3 | 244 |
| Chop Size | Count | Octets |
| 5 | 1 | 5 |
| 84 | 1 | 84 |
| 170 | 1 | 170 |
| Total | 3 | 259 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
000 RX OCTETS: 474554202f72756e436173653f636173653d313630266167656e743d7961776c20485454502f312e310d0a436f6e6e656374
696f6e3a206b6565702d616c6976 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e372e ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=3, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
í¿¿
003 TX OCTETS: 8103edbfbf
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 818355acadcd
006 RX OCTETS: b81312
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=82, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874
206d65737361676520617420706179 ...
008 TX OCTETS: 885203ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e6720746578
74206d6573736167652061742070 ...
009 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=3535616361646364
010 TCP DROPPED BY ME