Autobahn WebSocket Testsuite Report
Autobahn WebSocket

rust-websocket - Case 4.1.4 : Pass - 2 ms @ 2018-10-31T02:16:57.192Z

Case Description

Send small text message, then send frame with reserved non-control Opcode = 6 and non-empty payload, then send Ping.

Case Expectation

Echo for first message is received, but then connection is failed immediately, since reserved opcode frame is used. A Pong is not received.

Case Outcome

Actual events match at least one expected.

Expected:
{'NON-STRICT': [], 'OK': [('message', u'Hello, world!', False)]}

Observed:
[('message', u'Hello, world!', False)]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=38&agent=rust-websocket HTTP/1.1
Host: 127.0.0.1:9001
Connection: Upgrade
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: bd41xc9SQB3XsqV0moUILw==
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: yO4NVef+AJbzQ0A2Xni3MIC98uo=


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).
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
25125
1891189
Total2214

Octets Transmitted by Chop Size

Chop SizeCountOctets
212
414
15230
2061206
Total5242

Frames Received by Opcode

OpcodeCount
11
81
Total2

Frames Transmitted by Opcode

OpcodeCount
11
61
81
91
Total4


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d3338266167656e743d727573742d776562736f636b657420485454502f312e31
               0d0a486f73743a203132372e302e ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello, world!
003 TX OCTETS: 810d48656c6c6f2c20776f726c6421
004 TX FRAME : OPCODE=6, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               Hello, world!
005 TX OCTETS: 860d48656c6c6f2c20776f726c6421
006 TX FRAME : OPCODE=9, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
007 TX OCTETS: 8900
008 FAIL CONNECTION AFTER 1.000000 sec
009 RX OCTETS: 818d3039e69d785c8af15f15c6ea5f4b8af9118880f9b73388
010 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASKED=True, MASK=3330333965363964
               Hello, world!
011 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=6639623733333838
012 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
013 TX OCTETS: 880203e8
014 TCP DROPPED BY ME