Microsoft-HTTPAPI/2.0 - Case 6.21.5 : Fail - 2 ms @ 2021-01-02T08:46:49.795Z
Case Description
Send a text message with payload which is not valid UTF-8 in one fragment.
Payload: 0xedae80edb080
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
The connection was failed by the wrong endpoint (FAILED)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.7.5-0.10.9 Host: 127.0.0.1:9001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: IThP4/TETmU+QnXMQBFtYg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Server: Microsoft-HTTPAPI/2.0 Connection: Upgrade Sec-WebSocket-Accept: iMViMRVBYx7XvUE0Ycb9jPRCM9Q= Date: Sat, 02 Jan 2021 16:46:49 CST
| 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 | True | 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 | False | 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. |
| 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 | 1007 | The close code I sent in close frame (if any). |
| localCloseReason | encountered invalid UTF-8 while processing text message at payload octet index 1 | 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 |
| 8 | 1 | 8 |
| 197 | 1 | 197 |
| Total | 2 | 205 |
| Chop Size | Count | Octets |
| 12 | 1 | 12 |
| 88 | 1 | 88 |
| 240 | 1 | 240 |
| Total | 3 | 340 |
| Opcode | Count |
| 1 | 1 |
| Total | 1 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
352d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a5365727665723a204d69 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=6, MASK=5b88006a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
003 TX OCTETS: 81865b88006ab6268087eb08
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 8106edae80edb080
006 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=82, MASK=0ffec6f6, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e672074657874
206d65737361676520617420706179 ...
007 TX OCTETS: 88d20ffec6f60c11a3986c91b3987b9bb4936bdeaf98799faa9f6bde93a249d3fed67896af9a6adeb684609da3857c97a891
2f8aa38e7bdeab937c8da7916ade ...
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
009 TCP DROPPED BY ME