WebSockets Protocol Test Report
Autobahn WebSockets

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

Case Description

Send frame with reserved non-control Opcode = 4 and non-empty payload.

Case Expectation

The connection is failed immediately.

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: nddf7B0l7L09ZAsmno1Msg==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Server: AutobahnWebSockets/0.4.10
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: 69eYQ9Vsg6WDq8p5cXtjxzQh4c0=


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).
remoteCloseCode1002The close code the peer sent me in close frame (if any).
remoteCloseReasondata frame using reserved opcode 4The close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
38138
1641164
Total2202

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
29129
2011201
Total3238

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
41
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
               53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393030300d0a557067726164653a20776562736f
               636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a206e646466
               3742306c374c30395a41736d6e6f314d73673d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
               0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               576562536f636b6574732f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a
               20557067726164650d0a5365632d576562536f636b65742d4163636570743a20363965595139567367365744713870356358
               746a787a51683463303d0d0a0d0a
002 TX FRAME : OPCODE=4, FIN=True, RSV=0, MASK=6119930a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               reserved opcode payload
003 TX OCTETS: 84976119930a137ce06f136ff66e4176e3690e7df62a1178ea660e78f7
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 882403ea64617461206672616d65207573696e67207265736572766564206f70636f64652034
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
               ędata frame using reserved opcode 4
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=71c57f78, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
008 TX OCTETS: 888271c57f78722d
009 TCP DROPPED BY PEER