UnknownServer - Case 1.1.4 : Fail - 1002 ms @ 2021-02-12T11:12:48.939Z
Case Description
Send text message message with payload of length 127.
Case Expectation
Receive echo'ed text message (with payload as sent). Clean close with normal code.
Case Outcome
Actual events differ from any expected.
Expected:
{'OK': [('message', u'**************************************************************** ...', False)]}
Observed:
[('message', u'**************************************************************** ...', False), ('message', u'\x03\ufffd', False)]
Case Closing Behavior
The spec requires the connection to be failed cleanly here (UNCLEAN)
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: 9dgOp8Qi6H6xfn0KbKhATw== Sec-WebSocket-Version: 13
HTTP/1.1 101 WebSocket Protocol Handshake Upgrade: WebSocket Connection: Upgrade Sec-WebSocket-Accept: Lavx76uxrqp+QLVlENOPN9CmuZU=
| 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 | 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 |
| 131 | 1 | 131 |
| 138 | 1 | 138 |
| Total | 3 | 275 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 135 | 1 | 135 |
| 240 | 1 | 240 |
| Total | 3 | 383 |
| Opcode | Count |
| 1 | 2 |
| Total | 2 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120576562536f636b65742050726f746f636f6c2048616e647368616b650d0a55706772616465
3a20576562536f636b65740d0a43 ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=127, MASK=f3a69ea9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
**************************************************************** ...
003 TX OCTETS: 81fe007ff3a69ea9d98cb483d98cb483d98cb483d98cb483d98cb483d98cb483d98cb483d98cb483d98cb483d98cb483d98c
b483d98cb483d98cb483d98cb483 ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 817e007f2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a
2a2a2a2a2a2a2a2a2a2a2a2a2a2a ...
006 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=127, MASKED=False, MASK=None
**************************************************************** ...
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=5b0f5963, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
008 TX OCTETS: 88825b0f596358e7
009 RX OCTETS: 810403efbfbd
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=4, MASKED=False, MASK=None
�
011 FAILING CONNECTION
012 TCP DROPPED BY ME