Autobahn WebSockets Testsuite Report
Autobahn WebSockets

lluv-websocket (Lua 5.1 / WS) - Case 2.5 : Pass - 0 ms @ 2016-03-22T18:40:19.765Z

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: AutobahnTestSuite/0.7.1-0.10.0

Host: 127.0.0.1:9000

Upgrade: WebSocket

Connection: Upgrade

Pragma: no-cache

Cache-Control: no-cache

Sec-WebSocket-Key: mv0+8Celu6U23j9CO6cr6A==

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

Upgrade: websocket

Connection: upgrade

Sec-WebSocket-Accept: dWlTWSDwVji0mkH5f6NvaiMyuN4=


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.
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.
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).
remoteCloseReasonToo long payloadThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
20120
1291129
Total2149

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
1341134
2401240
Total3382

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
91
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
               312d302e31302e300d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=ad0de56b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
               fefefefefefefefefefefefefefefe ...
003 TX OCTETS: 89fe007ead0de56b53f31b9553f31b9553f31b9553f31b9553f31b9553f31b9553f31b9553f31b9553f31b9553f31b9553f3
               1b9553f31b9553f31b9553f31b95 ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 881203ea546f6f206c6f6e67207061796c6f6164
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=18, MASKED=False, MASK=None
               0x03ea546f6f206c6f6e67207061796c6f6164
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=d5cab762, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
008 TX OCTETS: 8882d5cab762d622
009 TCP DROPPED BY PEER