WebSockets Protocol Test Report
Autobahn WebSockets

AutobahnServer/0.4.10 - Case 6.19.1 : Pass - 1 ms @ 2012-01-09T14:43:20Z

Case Description

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

MESSAGE:
À€
c080

Case Expectation

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

Case Outcome

Actual events match at least one expected.

Expected:
{'OK': []}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnWebSocketsTestSuite/0.4.10
Host: localhost:9000
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: 4dicEt/KiCL3W5Y1uld98A==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Server: AutobahnWebSockets/0.4.10
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: MKE3YFvYKmeZfiO1Yedb+BZ+Oeo=


Closing Behavior

KeyValueDescription
isServerFalseTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeFalseTrue, 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.
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).
remoteCloseCode1007The close code the peer sent me in close frame (if any).
remoteCloseReasonencountered invalid UTF-8 while processing text message at payload octet index 0The close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
84184
1641164
Total2248

Octets Transmitted by Chop Size

Chop SizeCountOctets
8216
2011201
Total3217

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
11
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
               53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393030300d0a557067726164653a20776562736f
               636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2034646963
               45742f4b69434c3357355931756c643938413d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
               0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               576562536f636b6574732f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a
               20557067726164650d0a5365632d576562536f636b65742d4163636570743a204d4b4533594676594b6d655a66694f315965
               64622b425a2b4f656f3d0d0a0d0a
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=7cafa8c9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               
003 TX OCTETS: 81827cafa8c9bc2f
004 FAIL CONNECTION AFTER 0.500000 sec
005 RX OCTETS: 885203ef656e636f756e746572656420696e76616c6964205554462d38207768696c652070726f63657373696e6720746578
               74206d657373616765206174207061796c6f6164206f6374657420696e6465782030
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
               ïencountered invalid UTF-8 while processing text message at payload octet index 0
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=86cf0398, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
008 TX OCTETS: 888286cf03988527
009 TCP DROPPED BY PEER