WSServer (HTTP) - Case 5.13 : Pass - 2 ms @ 2020-12-10T23:39:19.351Z
Case Description
Send unfragmented Text Message after Continuation Frame with FIN = false, where there is nothing to continue, sent in per-frame 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: AutobahnTestSuite/0.8.1-0.10.9 Host: 127.0.0.1:9010 Upgrade: WebSocket Connection: Upgrade Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: P2WUZOxR5bIemuKo6plNxg== Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols Sec-Websocket-Accept: EXz6tg5PNIFEmeR3qkrsEQ6CnF4= Upgrade: websocket Connection: Upgrade Server: WSServer/v2.0.7
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 WebSocket 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 | 1002 | The close code the peer sent me in close frame (if any). |
remoteCloseReason | Experienced a protocol error | The close reason the peer sent me in close frame (if any). |
Chop Size | Count | Octets |
32 | 1 | 32 |
154 | 1 | 154 |
Total | 2 | 186 |
Chop Size | Count | Octets |
8 | 1 | 8 |
19 | 1 | 19 |
30 | 1 | 30 |
240 | 1 | 240 |
Total | 4 | 297 |
Opcode | Count |
8 | 1 |
Total | 1 |
Opcode | Count |
0 | 1 |
1 | 1 |
8 | 1 |
Total | 3 |
000 TX OCTETS: 474554202f20485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e382e
312d302e31302e390d0a486f7374 ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365632d576562736f636b65742d4163
636570743a2045587a3674673550 ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=c0b0fd51, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
non-continuation payload
003 TX OCTETS: 0098c0b0fd51aedf937ca3df9325a9de8830b4d9923fe0c09c28acdf9c35
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=c91f5b27, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=True
Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 818dc91f5b27817a374ba6337b50a66d3743e8
007 RX OCTETS: 881e03ea457870657269656e63656420612070726f746f636f6c206572726f72
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=30, MASKED=False, MASK=None
0x03ea457870657269656e63656420612070726f746f636f6c206572726f72
009 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=df740ecd, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
010 TX OCTETS: 8882df740ecddc9c
011 TCP DROPPED BY PEER