UnknownServer - Case 5.13 : Fail - 2004 ms @ 2021-02-12T11:14:57.586Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in per-frame chops.
Case Expectation
The connection is failed immediately, since there is no message to continue.
Case Outcome
Actual events differ from any expected.
Expected:
{'OK': []}
Observed:
[('message', u'non-continuation payloadHello, world!', False)]
Case Closing Behavior
The connection was failed by the wrong endpoint (FAILED)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.0-0.10.9 Host: 127.0.0.1:9001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: bOzONR4dsIRoy5uB2gCwdw== Sec-WebSocket-Version: 13
HTTP/1.1 101 WebSocket Protocol Handshake Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: CrkgJpy5euJfxL+fuzYbASmMTUY=
| 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 WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
| wasNotCleanReason | peer did not respond (in time) in closing handshake | 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 | True | 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 |
| 16 | 1 | 16 |
| 39 | 1 | 39 |
| 138 | 1 | 138 |
| Total | 3 | 193 |
| Chop Size | Count | Octets |
| 18 | 1 | 18 |
| 19 | 1 | 19 |
| 30 | 1 | 30 |
| 240 | 1 | 240 |
| Total | 4 | 307 |
| Opcode | Count |
| 1 | 2 |
| Total | 2 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120576562536f636b65742050726f746f636f6c2048616e647368616b650d0a55706772616465
3a20576562536f636b65740d0a43 ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=0cbcba34, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
non-continuation payload
003 TX OCTETS: 00980cbcba3462d3d4196fd3d44065d2cf5578d5d55a2cccdb4d60d3db50
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=7bb161c6, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 818d7bb161c633d40daa149d41b114c30da25a
007 RX OCTETS: 81256e6f6e2d636f6e74696e756174696f6e207061796c6f616448656c6c6f2c20776f726c6421
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=37, MASKED=False, MASK=None
non-continuation payloadHello, world!
009 FAILING CONNECTION
010 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=092ab79d, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e9476f696e672041776179
011 TX OCTETS: 888c092ab79d0ac3f0f26044d0bd485dd6e4
012 RX OCTETS: 810e03efbfbd476f696e672041776179
013 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
014 TCP DROPPED BY ME