Autobahn WebSocket Testsuite Report
Autobahn WebSocket

rust-websocket - Case 5.14 : Pass - 3 ms @ 2018-10-31T02:17:48.665Z

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 / HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.0-0.10.9
Host: 127.0.0.1:9002
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: jYct4JmVdgZMiLM2T010GA==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Sec-WebSocket-Accept: EG0wVSRjvAdgW+iBQ7JwlzTYO2c=
Connection: Upgrade
Upgrade: websocket


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.
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).
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
212
1291129
Total2131

Octets Transmitted by Chop Size

Chop SizeCountOctets
13232
2401240
Total33272

Frames Received by Opcode

OpcodeCount
81
Total1

Frames Transmitted by Opcode

OpcodeCount
01
11
81
Total3


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562536f636b65742d4163
               636570743a20454730775653526a ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=9634213c, 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=efc4462b, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
               Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 98
007 TX OCTETS: 96
008 TX OCTETS: 34
009 TX OCTETS: 21
010 TX OCTETS: 3c
011 TX OCTETS: f8
012 TX OCTETS: 5b
013 TX OCTETS: 4f
014 TX OCTETS: 11
015 TX OCTETS: f5
016 TX OCTETS: 5b
017 TX OCTETS: 4f
018 TX OCTETS: 48
019 TX OCTETS: ff
020 TX OCTETS: 5a
021 TX OCTETS: 54
022 TX OCTETS: 5d
023 TX OCTETS: e2
024 TX OCTETS: 5d
025 TX OCTETS: 4e
026 TX OCTETS: 52
027 TX OCTETS: b6
028 TX OCTETS: 44
029 TX OCTETS: 40
030 TX OCTETS: 45
031 TX OCTETS: fa
032 TX OCTETS: 5b
033 TX OCTETS: 40
034 TX OCTETS: 58
035 TX OCTETS: 81
036 TX OCTETS: 8d
037 RX OCTETS: 8800
038 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
039 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=10997311, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
040 TCP DROPPED BY PEER