Internet Explorer/11.472 - Case 9.4.9 : Pass - 896 ms @ 2019-01-06T17:13:19.349Z

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 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=276&agent=Internet%20Explorer/11.472 HTTP/1.1

Origin: null

Sec-WebSocket-Key: QPR5/U0F4jZRvITiRUx8kw==

Connection: Upgrade

Upgrade: websocket

Sec-WebSocket-Version: 13

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

Host: 127.0.0.1:9001

Cache-Control: no-cache
HTTP/1.1 101 Switching Protocols

Server: AutobahnTestSuite/0.8.1-0.10.9

X-Powered-By: AutobahnPython/0.10.9

Upgrade: WebSocket

Connection: Upgrade

Sec-WebSocket-Accept: K42ei9NvQSYzF6kxgzWwimPI1AQ=


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 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
616
3241324
27776127776
37774137774
65536634128768
Total674194648

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
2061206
419431414194314
Total34194524

Frames Received by Opcode

OpcodeCount
21
81
Total2

Frames Transmitted by Opcode

OpcodeCount
21
81
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323736266167656e743d496e7465726e65742532304578706c6f7265722f3131
               2e34373220485454502f312e310d ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               5465737453756974652f302e382e ...
002 CLOSE CONNECTION AFTER 100.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: 8880bd7550dc
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=6264373535306463
007 TCP DROPPED BY ME