rust-websocket - Case 6.2.2 : Pass - 1 ms @ 2018-10-31T02:16:59.357Z
Case Description
Send a valid UTF-8 text message in two fragments, fragmented on UTF-8 code point boundary.
MESSAGE FRAGMENT 1:
Hello-µ@ßöä
48656c6c6f2dc2b540c39fc3b6c3a4
MESSAGE FRAGMENT 2:
üàá-UTF-8!!
c3bcc3a0c3a12d5554462d382121
Case Expectation
The message is echo'ed back to us.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': [('message', u'Hello-\xb5@\xdf\xf6\xe4\xfc\xe0\xe1-UTF-8!!', False)]}
Observed:
[('message', u'Hello-\xb5@\xdf\xf6\xe4\xfc\xe0\xe1-UTF-8!!', False)]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=69&agent=rust-websocket HTTP/1.1 Host: 127.0.0.1:9001 Connection: Upgrade Upgrade: websocket Sec-WebSocket-Version: 13 Sec-WebSocket-Key: UvPxwYkdtRzuC+WYFUNzRg==
HTTP/1.1 101 Switching Protocols Server: AutobahnTestSuite/0.8.0-0.10.9 X-Powered-By: AutobahnPython/0.10.9 Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: bwz+rmfuHnTUBKKuRMCFOPZ0sC0=
| 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 | 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 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 | 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 |
| 6 | 1 | 6 |
| 35 | 1 | 35 |
| 189 | 1 | 189 |
| Total | 3 | 230 |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 16 | 1 | 16 |
| 17 | 1 | 17 |
| 206 | 1 | 206 |
| Total | 4 | 243 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| 8 | 1 |
| Total | 3 |
000 RX OCTETS: 474554202f72756e436173653f636173653d3639266167656e743d727573742d776562736f636b657420485454502f312e31
0d0a486f73743a203132372e302e ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=15, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello-µ@ßöä
003 TX OCTETS: 010f48656c6c6f2dc2b540c39fc3b6c3a4
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=14, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
üàá-UTF-8!!
005 TX OCTETS: 800ec3bcc3a0c3a12d5554462d382121
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 819d13a7f8005bc2946c7c8a3ab5536467c3a5645cc3af6458c3b28aad54558ac02132
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=29, MASKED=True, MASK=3133613766383030
Hello-µ@ßöäüàá-UTF-8!!
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 880203e8
011 RX OCTETS: 8880073bed57
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=3037336265643537
013 TCP DROPPED BY ME