Autobahn WebSocket Testsuite Report
Autobahn WebSocket

client - Case 6.2.2 : Pass - 7 ms @ 2023-02-24T01:25:10.708Z

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 match at least one expected.

Expected:
{'OK': [('message', u'Hello-\xb5@\xdf\xf6\xe4\xfc\xe0\xe1-UTF-8!!', False)]}

Observed:
[('message', u'Hello-\xb5@\xdf\xf6\xe4\xfc\xe0\xe1-UTF-8!!', False)]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=69&agent=client HTTP/1.1
Host: localhost:9002
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Key: 4aPhk8MHlWozBjFz4PO46Q==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.2-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: yWP6DRehZAH536fh3WYxlwtyzIw=


Closing Behavior

KeyValueDescription
isServerTrueTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, 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.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonNoneWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode1000The close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCode1000The close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
818
35135
1811181
Total3224

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
16116
17117
2061206
Total4243

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
01
11
81
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3639266167656e743d636c69656e7420485454502f312e310d0a486f73743a20
               6c6f63616c686f73743a39303032 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=15, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello-µ@ßöä
003 TX OCTETS: 010f48656c6c6f2dc2b540c39fc3b6c3a4
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=14, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               üàá-UTF-8!!
005 TX OCTETS: 800ec3bcc3a0c3a12d5554462d382121
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 819deeba5b44a6df3728819799f1ae79c4875879ff875279fb874f970e10a8976365cf
008 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=29, MASKED=True, MASK=6565626135623434
               Hello-µ@ßöäüàá-UTF-8!!
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 880203e8
011 RX OCTETS: 8882f7b018d3f458
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6637623031386433
               0x03e8
013 TCP DROPPED BY ME