wslay - Case 2.9 : Pass - 0 ms @ 2012-01-09T14:45:54Z
Case Description
Send unsolicited pong with payload. Send ping with payload. Verify pong for ping is received.
Case Expectation
Nothing in reply to own Pong, but Pong with payload echo'ed in reply to Ping. Clean close with normal code.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': [('pong', 'ping payload')]}
Observed:
[('pong', 'ping payload')]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnWebSocketsTestSuite/0.4.10 Host: localhost:9090 Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: hnbHNOB+yJRZrtKbHaT3iw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: STfLr8/YAL2K680jMRuIv4eOamU=
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 |
14 | 1 | 14 |
129 | 1 | 129 |
Total | 3 | 147 |
Chop Size | Count | Octets |
8 | 1 | 8 |
18 | 1 | 18 |
30 | 1 | 30 |
201 | 1 | 201 |
Total | 4 | 257 |
Opcode | Count |
8 | 1 |
10 | 1 |
Total | 2 |
Opcode | Count |
8 | 1 |
9 | 1 |
10 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393039300d0a557067726164653a20776562736f
636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a20686e6248
4e4f422b794a525a72744b624861543369773d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a20535466
4c72382f59414c324b3638306a4d5275497634654f616d553d0d0a0d0a
002 TX FRAME : OPCODE=10, FIN=True, RSV=0, MASK=6139fc07, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
unsolicited pong payload
003 TX OCTETS: 8a986139fc0714578f680d509f6e155c98271156926041499d7e0d569d63
004 TX FRAME : OPCODE=9, FIN=True, RSV=0, MASK=11170bf7, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
ping payload
005 TX OCTETS: 898c11170bf7617e659031676a8e7d786a93
006 CLOSE CONNECTION AFTER 1.000000 sec
007 RX OCTETS: 8a0c70696e67207061796c6f6164
008 RX FRAME : OPCODE=10, FIN=True, RSV=0, MASKED=False, MASK=None
ping payload
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=bc62ec98, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
è
010 TX OCTETS: 8882bc62ec98bf8a
011 RX OCTETS: 880203e8
012 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
è
013 TCP DROPPED BY PEER