lluv-websocket (Lua 5.1 / WS) - Case 6.4.3 : Fail - 2000 ms @ 2016-03-22T18:40:33.655Z
Case Description
Same as Case 6.4.1, but we send message not in 3 frames, but in 3 chops of the same message frame.
MESSAGE PARTS:
PART1 = cebae1bdb9cf83cebcceb5
PART2 = f4908080
PART3 = 656469746564
Case Expectation
The first chop is accepted, we expect to timeout on the first wait. The 2nd chop should be rejected immediately (fail fast on UTF-8). If we timeout, we expect the connection is failed at least then, since the complete message payload is not valid UTF-8.
Case Outcome
Actual events differ from any expected.
Expected:
{'NON-STRICT': [('timeout', 'A'), ('timeout', 'B')], 'OK': [('timeout', 'A')]}
Observed:
[('timeout', 'A'), ('timeout', 'B')]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.7.1-0.10.0 Host: 127.0.0.1:9000 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: JUgyF/zzS8SNnI+GANkt6w== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: upgrade Sec-WebSocket-Accept: gotbaweh4wrPuXVt8iTmJ/5CZF8=
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 | 1007 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | Invalid UTF8 character | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
26 | 1 | 26 |
129 | 1 | 129 |
Total | 2 | 155 |
Chop Size | Count | Octets |
4 | 1 | 4 |
6 | 3 | 18 |
8 | 1 | 8 |
11 | 1 | 11 |
240 | 1 | 240 |
Total | 7 | 281 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
0 | 1 |
8 | 1 |
Total | 2 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e372e
312d302e31302e300d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX OCTETS: 01953f41391d
003 TX OCTETS: f1fbd8a0868ebad3838f8c
004 DELAY 1.000000 sec for TAG A
005 DELAY TIMEOUT on TAG A
006 TX OCTETS: e9afc1b9
007 DELAY 1.000000 sec for TAG B
008 DELAY TIMEOUT on TAG B
009 TX OCTETS: 785b284d785b
010 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=0, MASK=12630c9f, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
011 TX OCTETS: 808012630c9f
012 FAIL CONNECTION AFTER 1.000000 sec
013 RX OCTETS: 881803ef496e76616c6964205554463820636861726163746572
014 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=24, MASKED=False, MASK=None
0x03ef496e76616c6964205554463820636861726163746572
015 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=975ecaea, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
016 TX OCTETS: 8882975ecaea94b6
017 TCP DROPPED BY PEER