Autobahn WebSockets Testsuite Report
Autobahn WebSockets

lluv-websocket - Case 9.2.4 : Pass - 2109 ms @ 2016-03-22T16:33:16.296Z

Case Description

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

Case Expectation

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

Case Outcome

Received binary message of length 4194304.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)



Opening Handshake

GET /runCase?case=260&agent=lluv-websocket HTTP/1.1

Host: 127.0.0.1:9001

Upgrade: websocket

Connection: Upgrade

Sec-WebSocket-Key: CdBToAxs2NkCY+THBtYNrA==

Sec-WebSocket-Version: 13

Sec-WebSocket-Protocol: echo

Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits
HTTP/1.1 101 Switching Protocols

Server: AutobahnTestSuite/0.7.1-0.10.0

Upgrade: WebSocket

Connection: Upgrade

Sec-WebSocket-Accept: ijFAhwecorvRLO5gy0JlKL/4/6A=


Closing Behavior

KeyValueDescription
isServerTrueTrue, 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.
droppedByMeTrueTrue, iff I dropped the TCP connection.
wasCleanTrueTrue, iff full WebSockets 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).
remoteCloseCode1000The 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
818
2901290
10136110136
13942113942
173762404170240
Total2444194616

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
1691169
419431414194314
Total34194487

Frames Received by Opcode

OpcodeCount
21
81
Total2

Frames Transmitted by Opcode

OpcodeCount
21
81
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323630266167656e743d6c6c75762d776562736f636b657420485454502f312e
               310d0a486f73743a203132372e30 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e372e ...
002 CLOSE CONNECTION AFTER 10.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
               0x03e8
004 TX OCTETS: 880203e8
005 RX OCTETS: 88822bb6f0fd285e
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASKED=True, MASK=3262623666306664
               0x03e8
007 TCP DROPPED BY ME