AutobahnClient/0.4.10 - Case 6.12.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:
¿
bf
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=109&agent=AutobahnClient/0.4.10 HTTP/1.1 User-Agent: AutobahnWebSockets/0.4.10 Host: localhost:9001 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: ZKedKbxXi9NxIHNz4Rdssw== Sec-WebSocket-Version: 8
HTTP/1.1 101 Switching Protocols Server: AutobahnWebSocketsTestSuite/0.4.10 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: elnwECluYG0AmxUPDW+igsgIspc=
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: 474554202f72756e436173653f636173653d313039266167656e743d4175746f6261686e436c69656e742f302e342e313020
485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b6574732f302e342e31300d0a48
6f73743a206c6f63616c686f73743a393030310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f
6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a205a4b65644b62785869394e7849484e7a345264
7373773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a20380d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
576562536f636b6574735465737453756974652f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f
6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20656c6e7745436c7559
4730416d78555044572b69677367497370633d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
¿
003 TX OCTETS: 8101bf
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 88d2f76ffa57f4809f3994008f39830a8832934f9339810e963e934faf03b142c2778007933b924f8a25980c9f2484069430
d71b9f2f834f9732841c9b30924f9b23d71f9b2e9b009b33d7009923921bda3e990b9f2fd75f
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=f76ffa57
ï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