Autobahn WebSocket Testsuite Report
Autobahn WebSocket

ws@6.2.0 - Case 5.15 : Pass - 2 ms @ 2019-03-09T17:18:36.594Z

Case Description

Send text Message fragmented into 2 fragments, then Continuation Frame with FIN = false where there is nothing to continue, then unfragmented Text Message, all sent in one chop.

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': [('message', u'fragment1fragment2', False)], 'NON-STRICT': []}

Observed:
[('message', u'fragment1fragment2', False)]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.0-0.10.9
Host: 192.168.0.109:9002
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: xvKFse0XC73MYxa9HpEGZw==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: o30xq1WF91wXYkAsQTWvWc0SODE=


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.
wasCleanFalseTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonpeer dropped the TCP connection without previous WebSocket closing handshakeWhen 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.
localCloseCodeNoneThe close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCodeNoneThe 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
20120
1291129
Total2149

Octets Transmitted by Chop Size

Chop SizeCountOctets
15460
2441244
Total5304

Frames Received by Opcode

OpcodeCount
11
Total1

Frames Transmitted by Opcode

OpcodeCount
02
12
Total4


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=33ec33b2, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment1
003 TX OCTETS: 018933ec33b2559e52d55e895dc602
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=4b92a25e, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment2
005 TX OCTETS: 80894b92a25e2de0c33926f7cc2a79
006 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=dbf020b8, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment3
007 TX OCTETS: 0089dbf020b8bd8241dfb6954ecce8
008 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=ed2a9951, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment4
009 TX OCTETS: 8189ed2a99518b58f836804ff725d9
010 FAIL CONNECTION AFTER 1.000000 sec
011 RX OCTETS: 8112667261676d656e7431667261676d656e7432
012 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=18, MASKED=False, MASK=None
               fragment1fragment2
013 TCP DROPPED BY PEER