wslay - Case 5.11 : Pass - 1 ms @ 2012-01-09T14:45:54Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = true, where there is nothing to continue, sent in octet-wise chops.
Case Expectation
The connection is failed immediately, since there is no message to continue.
Case Outcome
Actual events match at least one expected.
Expected:
{'OK': []}
Observed:
[]
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: w4AXzyxuCqeQ8LxObPaxag== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: KsSvV0WA/EYvJkN04XpS5N+QTF0=
| 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. |
| 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 | 1002 | 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 |
| 129 | 1 | 129 |
| Total | 2 | 133 |
| Chop Size | Count | Octets |
| 1 | 9 | 9 |
| 201 | 1 | 201 |
| Total | 10 | 210 |
| Opcode | Count |
| 8 | 1 |
| Total | 1 |
| Opcode | Count |
| 0 | 1 |
| 1 | 1 |
| 8 | 1 |
| Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e576562536f636b65747354657374
53756974652f302e342e31300d0a486f73743a206c6f63616c686f73743a393039300d0a557067726164653a20776562736f
636b65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4b65793a2077344158
7a79787543716551384c784f6250617861673d3d0d0a5365632d576562536f636b65742d56657273696f6e3a2031330d0a0d
0a
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e3a20557067726164650d0a5365632d576562536f636b65742d4163636570743a204b7353
76563057412f4559764a6b4e3034587053354e2b515446303d0d0a0d0a
002 TX FRAME : OPCODE=0, FIN=True, RSV=0, MASK=f35c2bc7, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
non-continuation payload
003 TX OCTETS: 80
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, MASK=14fc7b4a, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 98
007 TX OCTETS: f3
008 TX OCTETS: 5c
009 TX OCTETS: 2b
010 TX OCTETS: c7
011 TX OCTETS: 9d
012 TX OCTETS: 33
013 RX OCTETS: 880203ea
014 RX FRAME : OPCODE=8, FIN=True, RSV=0, MASKED=False, MASK=None
ê
015 TX FRAME : OPCODE=8, FIN=True, RSV=0, MASK=edfdd503, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
è
016 TX OCTETS: 45
017 TCP DROPPED BY PEER