Autobahn WebSocket Testsuite Report
Autobahn WebSocket

yawc - Case 5.11 : Pass - 9 ms @ 2018-04-16T14:00:45.275Z

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = true, 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=55&agent=yawc HTTP/1.1
Sec-WebSocket-Key: dzjsA0Oxam+QzzPkxe0SJg==
Host: autobahn-server:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Version: 13
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: Hl4AOSzwLSwVSNkBYnUsMj53WN4=


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


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
818
1851185
Total2193

Octets Transmitted by Chop Size

Chop SizeCountOctets
12828
2061206
Total29234

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
11
81
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3535266167656e743d7961776320485454502f312e310d0a5365632d57656253
               6f636b65742d4b65793a20647a6a ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e372e ...
002 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=24, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
               non-continuation payload
003 TX OCTETS: 80
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 TX OCTETS: 6e
010 TX OCTETS: 2d
011 TX OCTETS: 63
012 TX OCTETS: 6f
013 TX OCTETS: 6e
014 TX OCTETS: 74
015 TX OCTETS: 69
016 TX OCTETS: 6e
017 TX OCTETS: 75
018 TX OCTETS: 61
019 TX OCTETS: 74
020 TX OCTETS: 69
021 TX OCTETS: 6f
022 TX OCTETS: 6e
023 TX OCTETS: 20
024 TX OCTETS: 70
025 TX OCTETS: 61
026 TX OCTETS: 79
027 TX OCTETS: 6c
028 TX OCTETS: 6f
029 TX OCTETS: 61
030 TX OCTETS: 64
031 TX OCTETS: 81
032 TX OCTETS: 0d
033 RX OCTETS: 8882fc514ef5ffbb
034 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=6663353134656635
               0x03ea
035 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
036 TCP DROPPED BY ME