Autobahn WebSockets Testsuite Report
Autobahn WebSockets

yawl - Case 6.13.2 : Fail - 501 ms @ 2014-11-25T21:29:59.432Z

Case Description

Send a text message with payload which is not valid UTF-8 in one fragment.

Payload: 0xe020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.

Case Outcome

Actual events differ from any expected.

Expected:
{'OK': []}

Observed:
[('message', u'\ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd ', False)]

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)



Opening Handshake

GET /runCase?case=121&agent=yawl HTTP/1.1
Connection: keep-alive, Upgrade
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: 6zJ6yZs7FofkcPJ0ZrqMdg==
Host: localhost:9001
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.1-0.9.3-3
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: tHuvvnzDMZcddM/qQCSsFDRVhnk=


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).
failedByMeTrueTrue, 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 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.
localCloseCode1001The close code I sent in close frame (if any).
localCloseReasonGoing AwayThe close reason I sent in close frame (if any).
remoteCloseCodeNoneThe 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
6212
60160
2351235
Total4307

Octets Transmitted by Chop Size

Chop SizeCountOctets
14114
32132
1701170
Total3216

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d313231266167656e743d7961776c20485454502f312e310d0a436f6e6e656374
               696f6e3a206b6565702d616c6976 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e372e ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=30, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0xe020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20
003 TX OCTETS: 811ee020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 81bc22306795
006 RX OCTETS: cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8fdab5cd8f
               dab5cd8fdab5cd8fdab5
007 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=60, MASKED=True, MASK=3232333036373935
               � � � � � � � � � � � � � � �
008 FAILING CONNECTION
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=12, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e9476f696e672041776179
010 TX OCTETS: 880c03e9476f696e672041776179
011 RX OCTETS: 88808d8ab4b3
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=3864386162346233
013 TCP DROPPED BY ME