AutobahnServer/0.4.10 - Case 6.16.3 : Pass - 1 ms @ 2012-01-09T14:43:20Z
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
MESSAGE:
þþÿÿ
fefeffff
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 / HTTP/1.1 User-Agent: AutobahnWebSocketsTestSuite/0.4.10 Host: localhost:9000 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: 6KpSzO6V67Gh8NRG05FzcA== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnWebSockets/0.4.10 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: vkjLiW3f1ttPCAEN22sCtkYt4xI=
| 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 | 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 |
| 84 | 1 | 84 |
| 164 | 1 | 164 |
| Total | 2 | 248 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 10 | 1 | 10 |
| 201 | 1 | 201 |
| Total | 3 | 219 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393030300d0a557067726164653a20776562736f
636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a20364b7053
7a4f365636374768384e52473035467a63413d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
576562536f636b6574732f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a
20557067726164650d0a5365632d576562536f636b65742d4163636570743a20766b6a4c69573366317474504341454e3232
7343746b59743478493d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=7ff93b80, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
þþÿÿ
003 TX OCTETS: 81847ff93b808107c47f
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 885203ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e6720746578
74206d657373616765206174207061796c6f6164206f6374657420696e6465782030
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
ïencountered invalid UTF-8 while processing text message at payload octet index 0
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=68da9508, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
è
008 TX OCTETS: 888268da95086b32
009 TCP DROPPED BY PEER