AutobahnServer/0.4.10 - Case 9.8.4 : Pass - 478 ms @ 2012-01-09T14:45:49Z
Case Description
Send 1000 binary messages of payload size 256 to measure implementation/network RTT (round trip time) / latency.
Case Expectation
Receive echo'ed binary messages (with payload as sent). Timeout case after 120 secs.
Case Outcome
Ok, received all echo'ed messages in time.
Expected:
{}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnWebSocketsTestSuite/0.4.10 Host: localhost:9000 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: iUgmVJL7bRRYidVQHIIhtw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Server: AutobahnWebSockets/0.4.10 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: BCOp/V4d6nWfNYrPF7A1hJASiuI=
| Key | Value | Description |
| isServer | False | True, iff I (the fuzzer) am a server, and the peer is a client. |
| closedByMe | True | 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. |
| 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 | 1000 | The close code the peer sent me in close frame (if any). |
| remoteCloseReason | None | The close reason the peer sent me in close frame (if any). |
| Chop Size | Count | Octets |
| 4 | 1 | 4 |
| 164 | 1 | 164 |
| 260 | 1000 | 260000 |
| Total | 1002 | 260168 |
| Chop Size | Count | Octets |
| 8 | 1 | 8 |
| 201 | 1 | 201 |
| 264 | 1000 | 264000 |
| Total | 1002 | 264209 |
| Opcode | Count |
| 2 | 1000 |
| 8 | 1 |
| Total | 1001 |
| Opcode | Count |
| 2 | 1000 |
| 8 | 1 |
| Total | 1001 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393030300d0a557067726164653a20776562736f
636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a206955676d
564a4c3762525259696456514849496874773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
576562536f636b6574732f302e342e31300d0a557067726164653a20776562736f636b65740d0a436f6e6e656374696f6e3a
20557067726164650d0a5365632d576562536f636b65742d4163636570743a2042434f702f563464366e57664e5972504637
4131684a41536975493d0d0a0d0a
002 WIRELOG DISABLED
003 CLOSE CONNECTION AFTER 120.000000 sec
004 WIRELOG ENABLED
005 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=b8b2679f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
è
006 TX OCTETS: 8882b8b2679fbb5a
007 RX OCTETS: 880203e8
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
è
009 TCP DROPPED BY PEER