sgcWebSockets - Case 9.2.3 : Pass - 608 ms @ 2013-03-03T15:45:11Z

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.5.2-0.5.9

Host: 127.0.0.1:5500

Upgrade: WebSocket

Connection: Upgrade

Pragma: no-cache

Cache-Control: no-cache

Sec-WebSocket-Key: fXmmF2Rc7QvhxwYgYta0Ig==

Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols

Upgrade: websocket

Connection: Upgrade

Sec-WebSocket-Accept: 1NEpvQ8qO8CRVipE03uPcW9NHrE=


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 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
414
1291129
3472724304
694423159712
1041651531216
1388823319424
13930113930
Total1071048719

Octets Transmitted by Chop Size

Chop SizeCountOctets
818
2391239
104859011048590
Total31048837

Frames Received by Opcode

OpcodeCount
21
81
Total2

Frames Transmitted by Opcode

OpcodeCount
21
81
Total2


Wire Log

000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
               322d302e352e390d0a486f73743a203132372e302e302e313a353530300d0a557067726164653a20576562536f636b65740d
               0a436f6e6e656374696f6e3a20557067726164650d0a507261676d613a206e6f2d63616368650d0a43616368652d436f6e74
               726f6c3a206e6f2d63616368650d0a5365632d576562536f636b65742d4b65793a2066586d6d463252633751766878775967
               5974613049673d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
               65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20314e45
               70765138714f38435256697045303375506357394e4872453d0d0a0d0a
002 CLOSE CONNECTION AFTER 10.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=9a7f8944, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
004 TX OCTETS: 88829a7f89449997
005 RX OCTETS: 880203e8
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
007 TCP DROPPED BY PEER