Autobahn WebSockets Testsuite Report
Autobahn WebSockets

AutobahnServer - Case 6.2.1 : Pass - 2 ms @ 2017-11-02T08:57:12Z

Case Description

Send a valid UTF-8 text message in one fragment.

MESSAGE:
Hello-µ@ßöäüàá-UTF-8!!
48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121

Case Expectation

The message is echo'ed back to us.

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': [('message', '0x48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121', False)]}

Observed:
[('message', '0x48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121', False)]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.5.5-0.5.14
Host: localhost:9000
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: jPJALx2mobO4ObjkqnqhLA==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Server: AutobahnPython/0.5.14
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: CZuctuAVIsByJwjF4649WXYzZhg=


Closing Behavior

KeyValueDescription
isServerFalseTrue, 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.
droppedByMeFalseTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSockets 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
414
31131
1601160
Total3195

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
35135
2401240
Total3283

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
               352d302e352e31340d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               507974686f6e2f302e352e31340d ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=29, MASK=809c41d9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121
003 TX OCTETS: 819d809c41d9c8f92db5efb1836cc05fde1a365fe51a3c5fe11a21b1148dc6b179f8a1
004 CLOSE CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 811d48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121
006 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=29, MASKED=False, MASK=None
               0x48656c6c6f2dc2b540c39fc3b6c3a4c3bcc3a0c3a12d5554462d382121
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=db208bb0, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
008 TX OCTETS: 8882db208bb0d8c8
009 RX OCTETS: 880203e8
010 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=False, MASK=None
               0x03e8
011 TCP DROPPED BY PEER