WebSockets Protocol Test Report
Autobahn WebSockets

wslay - Case 2.5 : Pass - 0 ms @ 2012-01-09T14:45:54Z

Case Description

Send ping with binary payload of 126 octets.

Case Expectation

Connection is failed immediately (1002/Protocol Error), since control frames are only allowed to have payload up to and including 125 octets..

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:9090
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: A8Km5Q7pLhQ+98rYkop6Zw==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: JsuVwjh6Mavw7ULzIQ5ivO0f3sU=


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).
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
1291129
Total2131

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
1341134
2011201
Total3343

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
91
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
               53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393039300d0a557067726164653a20776562736f
               636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2041384b6d
               355137704c68512b393872596b6f70365a773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
               0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a204a7375
               56776a68364d61767737554c7a49513569764f30663373553d0d0a0d0a
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, MASK=1fa0d769, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               þþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþþ
               þþþþþþþþþþþþþþþþþþþþþþþþþþ
003 TX OCTETS: 89fe007e1fa0d769e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e
               2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997
               e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e2997e15e
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 8800
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=33773bd9, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
008 TX OCTETS: 888233773bd9309f
009 TCP DROPPED BY PEER