AutobahnPython - Case 9.2.6 : Fail - 189 ms @ 2014-12-01T19:26:08.792Z
Case Description
Send binary message message with payload of length 16 * 2**20 (16M).
Case Expectation
Receive echo'ed binary message (with payload as sent).
Case Outcome
Did not receive message within 100 seconds.
Expected:
{}
Observed:
[]
Case Closing Behavior
The connection was failed by the wrong endpoint (FAILED)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.7.1-0.9.3-3 Host: 127.0.0.1:9001 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: t2I3diKiJquRT9luXAo52A== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: vsv5C+MPY7YaDeDSC9AYg5fgvko=
| Key | Value | Description |
| isServer | False | True, iff I (the fuzzer) am a server, and the peer is a client. |
| closedByMe | False | True, iff I have initiated closing handshake (that is, did send close first). |
| failedByMe | False | True, 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. |
| droppedByMe | False | True, iff I dropped the TCP connection. |
| wasClean | True | True, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
| wasNotCleanReason | None | When wasClean == False, the reason what happened. |
| wasServerConnectionDropTimeout | False | When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True. |
| wasOpenHandshakeTimeout | False | When performing the opening handshake, but the peer did not finish in time, this gets True. |
| wasCloseHandshakeTimeout | False | When we initiated a closing handshake, but the peer did not respond in time, this gets True. |
| localCloseCode | 1000 | The close code I sent in close frame (if any). |
| localCloseReason | None | The close reason I sent in close frame (if any). |
| remoteCloseCode | 1009 | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | exceeded max frame size | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 2 | 1 | 2 |
| 25 | 1 | 25 |
| 129 | 1 | 129 |
| Total | 3 | 156 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 241 | 1 | 241 |
| 16777230 | 1 | 16777230 |
| Total | 3 | 16777479 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 2 | 1 |
| 8 | 1 |
| Total | 2 |
Wire log after handshake disabled!
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
312d302e392e332d330d0a486f73 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 CLOSE CONNECTION AFTER 100.000000 sec
003 TCP DROPPED BY PEER