Autobahn WebSocket Testsuite Report
Autobahn WebSocket

ixwebsocket - Case 5.18 : Pass - 3 ms @ 2020-01-09T22:33:44.063Z

Case Description

Send text Message fragmented into 2 fragments, with both frame opcodes set to text, sent in one chop.

Case Expectation

The connection is failed immediately, since all data frames after the initial data frame must have opcode 0.

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=62&agent=ixwebsocket HTTP/1.1
Host: localhost:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: c1feh4D8G6b00fg52E10gf==
User-Agent: ixwebsocket/7.9.2 macos ssl/DarwinSSL zlib 1.2.11
Sec-WebSocket-Extensions: permessage-deflate; server_max_window_bits=15; client_max_window_bits=15
HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.8.0-0.10.9
X-Powered-By: AutobahnPython/0.10.9
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: 77FJdn0z5T25Thslzk3b5FkAc94=


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).
remoteCloseReasonFragmentation: data message out of sequenceThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
51151
3491349
Total2400

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
11222
2061206
Total4232

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
12
81
Total3


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3632266167656e743d6978776562736f636b657420485454502f312e310d0a48
               6f73743a206c6f63616c686f7374 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment1
003 TX OCTETS: 0109667261676d656e7431
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               fragment2
005 TX OCTETS: 8109667261676d656e7432
006 FAIL CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 88ad5e17aa485dfdec3a3f70c72d3063cb3c3778c4727e73cb3c3f37c72d2d64cb2f3b37c53d2a37c52e7e64cf392b72c42b
               3b
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=45, MASKED=True, MASK=3565313761613438
               0x03ea467261676d656e746174696f6e3a2064617461206d657373616765206f7574206f662073657175656e6365
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