wsgo fuzzing client - Case 6.2.2 : Fail - 1002 ms @ 2025-03-31T15:47:08.755Z
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 differ from any expected.
Expected:
{'OK': [('message', u'Hello-\xb5@\xdf\xf6\xe4\xfc\xe0\xe1-UTF-8!!', False)]}
Observed:
[('message', u'Hello-\xb5@\xdf\xf6\xe4', False)]
Case Closing Behavior
It is preferred that the server close the TCP connection (FAILED BY CLIENT)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.8.2-0.10.9 Host: localhost:8080 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: XaZ7nKc6KFAmfJCY4AvnTQ== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Connection: Upgrade Sec-Websocket-Accept: WuTNVeZEOswKZz96sfoxn17I1wo= 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 | 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 | 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 | None | 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 |
| 4 | 1 | 4 |
| 17 | 1 | 17 |
| 129 | 1 | 129 |
| Total | 3 | 150 |
| Chop Size | Count | Octets |
| 6 | 1 | 6 |
| 20 | 1 | 20 |
| 21 | 1 | 21 |
| 240 | 1 | 240 |
| Total | 4 | 287 |
| Opcode | Count |
| 1 | 1 |
| 8 | 1 |
| Total | 2 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
322d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a436f6e6e656374696f6e3a2055706772
6164650d0a5365632d576562736f ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=15, MASK=b79e1fd1, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
Hello-µ@ßöä
003 TX OCTETS: 018fb79e1fd1fffb73bdd8b3dd64f75d8012015dbb
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=14, MASK=d9f9e549, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
üàá-UTF-8!!
005 TX OCTETS: 808ed9f9e5491a4526e91a58c81c8dbfc871f8d8
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 810f48656c6c6f2dc2b540c39fc3b6c3a4
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=15, MASKED=False, MASK=None
Hello-µ@ßöä
009 CLOSING CONNECTION
010 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=78e3e5d3, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
011 TX OCTETS: 888078e3e5d3
012 RX OCTETS: 880003ea
013 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
014 TCP DROPPED BY ME