WebSockets Protocol Test Report
Autobahn WebSockets

tootallnate/websocket - Case 6.20.1 : Fail - 501 ms @ 2012-02-04T15:41:19Z

Case Description

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

MESSAGE:
í €
eda080

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', '?', False)]

Case Closing Behavior

The connection was failed by the wrong endpoint (FAILED)



Opening Handshake

GET / HTTP/1.1

User-Agent: AutobahnWebSocketsTestSuite/0.4.10

Host: localhost:9003

Upgrade: websocket

Connection: Upgrade

Sec-WebSocket-Key: 8hQi20KtwNAl024fziMiZA==

Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols

Upgrade: websocket

Connection: Upgrade

Sec-WebSocket-Accept: 2vQQWjYeEC/rYsn25QkOUP1J64E=


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).
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.
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.
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
212
313
1291129
Total3134

Octets Transmitted by Chop Size

Chop SizeCountOctets
919
18118
2011201
Total3228

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
               53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393030330d0a557067726164653a20776562736f
               636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2038685169
               32304b74774e416c303234667a694d695a413d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
               0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20327651
               51576a596545432f7259736e3235516b4f5550314a3634453d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=09392f03, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               í €
003 TX OCTETS: 818309392f03e499af
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 81013f
006 RX FRAME : OPCODE=1, FIN=True, RSV=0, MASKED=False, MASK=None
               ?
007 FAILING CONNECTION
008 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=1a762475, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               éGoing Away
009 TX OCTETS: 888c1a762475199f631a731843555b01450c
010 RX OCTETS: 8800
011 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
012 TCP DROPPED BY PEER