Autobahn WebSocket Testsuite Report
Autobahn WebSocket

Pawl/0.3 - Case 2.5 : Pass - 3 ms @ 2017-10-12T00:31:19.108Z

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 /runCase?case=21&agent=Pawl/0.3 HTTP/1.1
Host: 127.0.0.1:9001
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: WDBQRmgzMWhlSzZJK3JyZQ==
User-Agent: Ratchet-Pawl/0.2.3
Origin: http://127.0.0.1
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.6-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: yZXhe/EreomUd0WA3TlBZCSwe3k=


Closing Behavior

KeyValueDescription
isServerTrueTrue, 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.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSocket 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).
remoteCloseReasonRatchet detected a mismatch between final bit and indicated payload lengthThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
82182
2411241
Total2323

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
1301130
2061206
Total3340

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
81
91
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3231266167656e743d5061776c2f302e3320485454502f312e310d0a486f7374
               3a203132372e302e302e313a3930 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e372e ...
002 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=126, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0xfefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
               fefefefefefefefefefefefefefefe ...
003 TX OCTETS: 897e007efefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefe
               fefefefefefefefefefefefefefe ...
004 FAIL CONNECTION AFTER 1.000000 sec
005 RX OCTETS: 88cc505f544b53b5062a243c3c2e247f302e243a373f353b742a70323d383d3e2028387f362e2428312e3e7f32223e3e386b
               3236206b3131306b39313022333e ...
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=76, MASKED=True, MASK=3530356635343462
               0x03ea526174636865742064657465637465642061206d69736d61746368206265747765656e2066696e616c206269742061
               6e6420696e64696361746564207061 ...
007 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
008 TX OCTETS: 880203e8
009 TCP DROPPED BY ME