Microsoft-HTTPAPI/2.0 - Case 3.5 : Fail - 2006 ms @ 2021-01-02T08:45:36.190Z
Case Description
Send small binary message with RSV = 5.
Case Expectation
The connection is failed immediately, since RSV must be 0.
Case Outcome
Actual events differ from any expected.
Expected:
{'OK': []}
Observed:
[('message', '0x00fffefdfcfb00ff', True)]
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: tK5PA6UxTIHuseYD3K2FoQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Server: Microsoft-HTTPAPI/2.0 Connection: Upgrade Sec-WebSocket-Accept: iAKO7WBlPvN2kedkoTQiAqIVGvY= Date: Sat, 02 Jan 2021 16:45:36 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 | server did not drop TCP connection (in time) | When wasClean == False, the reason what happened. |
| wasServerConnectionDropTimeout | True | 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 | 1001 | The close code I sent in close frame (if any). |
| localCloseReason | Going Away | 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 |
| 10 | 1 | 10 |
| 197 | 1 | 197 |
| Total | 3 | 209 |
| Chop Size | Count | Octets |
| 14 | 1 | 14 |
| 18 | 1 | 18 |
| 240 | 1 | 240 |
| Total | 3 | 272 |
| Opcode | Count |
| 2 | 1 |
| 8 | 1 |
| Total | 2 |
| Opcode | Count |
| 2 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
352d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a5365727665723a204d69 ...
002 TX FRAME : OPCODE=2, FIN=True, RSV=5, PAYLOAD-LEN=8, MASK=3b383bf9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x00fffefdfcfb00ff
003 TX OCTETS: d2883b383bf93bc7c504c7c33b06
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 820800fffefdfcfb00ff
006 RX FRAME : OPCODE=2, FIN=True, RSV=0, PAYLOAD-LEN=8, MASKED=False, MASK=None
0x00fffefdfcfb00ff
007 FAILING CONNECTION
008 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=2dd5b20f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e9476f696e672041776179
009 TX OCTETS: 888c2dd5b20f2e3cf56044bbd52f6ca2d376
010 RX OCTETS: 8800
011 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
012 TCP DROPPED BY ME