ServerFrameworkServer/6.9 - Case 5.15 : Pass - 1 ms @ 2017-11-02T08:50:58Z
Case Description
Send text Message fragmented into 2 fragments, then Continuation Frame with FIN = false where there is nothing to continue, then unfragmented Text Message, all sent in one chop.
Case Expectation
The connection is failed immediately, since there is no message to continue.
Case Outcome
Actual events match at least one expected.
Expected:
{'NON-STRICT': [], 'OK': [('message', '0x667261676d656e7431667261676d656e7432', False)]}
Observed:
[('message', '0x667261676d656e7431667261676d656e7432', False)]
Case Closing Behavior
Connection was properly closed (OK)
GET / HTTP/1.1 User-Agent: AutobahnTestSuite/0.5.5-0.5.14 Host: localhost:5050 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: vZVk3mfMygnnG/Y7GoofCw== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Upgrade: websocket Connection: Upgrade Sec-WebSocket-Accept: 4XENz6YOh6cl7HOkD1rlsn7TquQ=
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 | False | True, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility). |
wasNotCleanReason | peer dropped the TCP connection without previous WebSocket closing handshake | 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 | None | The close code I sent in close frame (if any). |
localCloseReason | None | The close reason I sent in close frame (if any). |
remoteCloseCode | None | 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 |
20 | 1 | 20 |
129 | 1 | 129 |
Total | 2 | 149 |
Chop Size | Count | Octets |
15 | 4 | 60 |
240 | 1 | 240 |
Total | 5 | 300 |
Opcode | Count |
1 | 1 |
Total | 1 |
Opcode | Count |
0 | 2 |
1 | 2 |
Total | 4 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e352e
352d302e352e31340d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a557067726164653a20776562736f636b
65740d0a436f6e6e656374696f6e ...
002 TX FRAME : OPCODE=1, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=9b607ef8, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x667261676d656e7431
003 TX OCTETS: 01899b607ef8fd121f9ff605108caa
004 TX FRAME : OPCODE=0, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=f20d4088, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x667261676d656e7432
005 TX OCTETS: 8089f20d4088947f21ef9f682efcc0
006 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=9, MASK=9aa82abd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x667261676d656e7433
007 TX OCTETS: 00899aa82abdfcda4bdaf7cd44c9a9
008 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=9, MASK=b8d6d650, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x667261676d656e7434
009 TX OCTETS: 8189b8d6d650dea4b737d5b3b8248c
010 FAIL CONNECTION AFTER 1.000000 sec
011 RX OCTETS: 8112667261676d656e7431667261676d656e7432
012 RX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=18, MASKED=False, MASK=None
0x667261676d656e7431667261676d656e7432
013 TCP DROPPED BY PEER