Autobahn WebSocket Testsuite Report
Autobahn WebSocket

Pawl/0.3 - Case 5.10 : Pass - 2 ms @ 2017-10-12T00:31:19.240Z

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in per-frame chops.

Case Expectation

The connection is failed immediately, since there is no message to continue.

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=54&agent=Pawl/0.3 HTTP/1.1
Host: 127.0.0.1:9001
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: aC9ybUZDQTlHcjF0Z1ZOQw==
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: 3Oi6nRHAt5C6Pn4oSjblHNDt1LQ=


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 the first frame of a message was a continueThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
68168
2411241
Total2309

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
15115
26126
2061206
Total4251

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
11
81
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3534266167656e743d5061776c2f302e3320485454502f312e310d0a486f7374
               3a203132372e302e302e313a3930 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e372e ...
002 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
               non-continuation payload
003 TX OCTETS: 80186e6f6e2d636f6e74696e756174696f6e207061796c6f6164
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
               Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 810d48656c6c6f2c20776f726c6421
007 RX OCTETS: 88be636c2f4760867d26170f4722174c4b2217094c3306080f330b090f210a1e5c33430a5d260e090f28054c4e670e095c34
               020b4a67140d5c67024c4c280d18 ...
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=62, MASKED=True, MASK=3633366332663437
               0x03ea5261746368657420646574656374656420746865206669727374206672616d65206f662061206d6573736167652077
               6173206120636f6e74696e7565 ...
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
010 TX OCTETS: 880203e8
011 TCP DROPPED BY ME