rust-websocket - Case 6.2.2 : Pass - 1 ms @ 2018-10-31T02:17:50.694Z
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 / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.0-0.10.9 Host: 127.0.0.1:9002 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: SBPYRjGNE0z7ll2EXp0HHQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Sec-WebSocket-Accept: X75TkoijU1E94HpJwdPizjjdMEA= Connection: Upgrade Upgrade: websocket
| Key | Value | Description |
| isServer | False | 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 | False | 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 |
| 2 | 1 | 2 |
| 31 | 1 | 31 |
| 129 | 1 | 129 |
| Total | 3 | 162 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 20 | 1 | 20 |
| 21 | 1 | 21 |
| 240 | 1 | 240 |
| Total | 4 | 289 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562536f636b65742d4163
636570743a20583735546b6f696a ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=15, MASK=d6ea76cf, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello-µ@ßöä
003 TX OCTETS: 018fd6ea76cf9e8f1aa3b9c7b47a9629e90c6029d2
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=14, MASK=e9797efa, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
üàá-UTF-8!!
005 TX OCTETS: 808ee9797efa2ac5bd5a2ad853afbd3f53c2c858
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 811d48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=29, MASKED=False, MASK=None
Hello-µ@ßöäüàá-UTF-8!!
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=d82b7eb9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 8882d82b7eb9dbc3
011 RX OCTETS: 8800
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
013 TCP DROPPED BY PEER