WebSockets Protocol Test Report
Autobahn WebSockets

AutobahnClient/0.4.10 - Case 9.6.2 : Pass - 965 ms @ 2012-01-09T14:56:04Z

Case Description

Send binary message message with payload of length 1 * 2**20 (1M). Sent out data in chops of 128 octets.

Case Expectation

Receive echo'ed text 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 /runCase?case=278&agent=AutobahnClient/0.4.10 HTTP/1.1
User-Agent: AutobahnWebSockets/0.4.10
Host: localhost:9001
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: okm1WAZol76ABSb4WRYReA==
Sec-WebSocket-Version: 8
HTTP/1.1 101 Switching Protocols
Server: AutobahnWebSocketsTestSuite/0.4.10
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: xL8ZpYF9uw3axCRRrOUOh3ZpBuw=


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.
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
2351235
16398116398
49152149152
6553615983040
Total191048833

Octets Transmitted by Chop Size

Chop SizeCountOctets
414
10110
12881921048576
1731173
Total81951048763

Frames Received by Opcode

OpcodeCount
21
81
Total2

Frames Transmitted by Opcode

OpcodeCount
21
81
Total2


Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323738266167656e743d4175746f6261686e436c69656e742f302e342e313020
               485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b6574732f302e342e31300d0a48
               6f73743a206c6f63616c686f73743a393030310d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f
               6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a206f6b6d3157415a6f6c37364142536234575259
               5265413d3d0d0a5365632d576562536f636b65742d56657273696f6e3a20380d0a0d0a
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
               576562536f636b6574735465737453756974652f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f
               6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20784c385a7059463975
               77336178435252724f554f68335a704275773d0d0a0d0a
002 CLOSE CONNECTION AFTER 600.000000 sec
003 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
004 TX OCTETS: 880203e8
005 RX OCTETS: 88829932db179ada
006 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=True, MASK=9932db17
007 TCP DROPPED BY ME