Autobahn WebSocket Testsuite Report
Autobahn WebSocket

rust-websocket - Case 9.2.3 : Pass - 164 ms @ 2018-10-31T02:18:04.028Z

Case Description

Send binary message message with payload of length 1 * 2**20 (1M).

Case Expectation

Receive echo'ed binary message (with payload as sent).

Case Outcome

Received binary message of length 1048576.

Expected:
{}

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: i+eryu7eBPR4MqAPTMD8wA==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Sec-WebSocket-Accept: 5RewuUTsZ9ilqG3oE9FeCyDjSb8=
Connection: Upgrade
Upgrade: websocket


Closing Behavior

KeyValueDescription
isServerFalseTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeTrueTrue, 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
20746120746
44800144800
6553615983040
Total191048717

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
2401240
104859011048590
Total31048838

Frames Received by Opcode

OpcodeCount
21
81
Total2

Frames Transmitted by Opcode

OpcodeCount
21
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
               302d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562536f636b65742d4163
               636570743a203552657775555473 ...
002 CLOSE CONNECTION AFTER 10.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=2d59d6a3, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
004 TX OCTETS: 88822d59d6a32eb1
005 RX OCTETS: 8800
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=False, MASK=None
007 TCP DROPPED BY PEER