AutobahnClient/0.4.10 - Case 6.16.2 : Pass - 1 ms @ 2012-01-09T14:53:51Z
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
ÿ
ff
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
Connection was properly closed (OK)
GET /runCase?case=133&agent=AutobahnClient/0.4.10 HTTP/1.1 User-Agent: AutobahnWebSockets/0.4.10 Host: localhost:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: Hb4SoAjvopjUa4dEDab57Q== Sec-WebSocket-Version: 8
HTTP/1.1 101 Switching Protocols Server: AutobahnWebSocketsTestSuite/0.4.10 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: uSH8wKNIgZKZKu3O+CS+8Rob/hk=
| Key | Value | Description |
| isServer | True | 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 | True | 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 | 1007 | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | encountered invalid UTF-8 while processing text message at payload octet index 0 | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 88 | 1 | 88 |
| 235 | 1 | 235 |
| Total | 2 | 323 |
| Chop Size | Count | Octets |
| 3 | 1 | 3 |
| 4 | 1 | 4 |
| 173 | 1 | 173 |
| Total | 3 | 180 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
000 RX OCTETS: 474554202f72756e436173653f636173653d313333266167656e743d4175746f6261686e436c69656e742f302e342e313020
485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b6574732f302e342e31300d0a48
6f73743a206c6f63616c686f73743a393030310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f
6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a20486234536f416a766f706a5561346445446162
3537513d3d0d0a5365632d576562536f636b65742d56657273696f6e3a20380d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
576562536f636b6574735465737453756974652f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f
6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a2075534838774b4e4967
5a4b5a4b75334f2b43532b38526f622f686b3d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
ÿ
003 TX OCTETS: 8101ff
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 88d291bd1abd92527fd3f2d26fd3e5d868d8f59d73d3e7dc76d4f59d4fe9d790229de6d573d1f49d6acffede7fcee2d474da
b1c97fc5e59d77d8e2ce7bdaf49d7bc9b1cd7bc4fdd27bd9b1d279c9f4c93ad4ffd97fc5b18d
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=91bd1abd
ïencountered invalid UTF-8 while processing text message at payload octet index 0
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
è
008 TX OCTETS: 880203e8
009 TCP DROPPED BY ME