Autobahn WebSockets Testsuite Report
Autobahn WebSockets

PocketSocketClient - Case 5.14 : Pass - 1 ms @ 2016-03-30T11:13:41.824Z

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in octet-wise 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=58&agent=PocketSocketClient HTTP/1.1
Host: localhost:9001
Sec-WebSocket-Key: /6cO3UxMiQ/xNrFseY8zWw==
Sec-WebSocket-Version: 13
Upgrade: websocket
Origin: http://localhost:9001
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
Connection: upgrade
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.5-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: BCXGI6b0coK1VgjA4XfVEDcAzk8=


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 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).
remoteCloseReasonData continuation frames must follow an initial data frameThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
66166
2991299
Total2365

Octets Transmitted by Chop Size

Chop SizeCountOctets
144
2061206
Total5210

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
11
81
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3538266167656e743d636f6d2e7a776f70706c652e5053576562536f636b6574
               20485454502f312e310d0a486f73 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e372e ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
               non-continuation payload
003 TX OCTETS: 00
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
               Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 18
007 TX OCTETS: 6e
008 TX OCTETS: 6f
009 RX OCTETS: 88bc93bcdece90569aafe7ddfeadfcd2aaa7fdc9bfbafad3b0eef5cebfa3f6cffea3e6cfaaeef5d3b2a2fccbfeaffd9cb7a0
               fac8b7afff9cbaafe7ddfea8e1dd ...
010 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=60, MASKED=True, MASK=3933626364656365
               0x03ea4461746120636f6e74696e756174696f6e206672616d6573206d75737420666f6c6c6f7720616e20696e697469616c
               2064617461206672616d65
011 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
012 TCP DROPPED BY ME