Autobahn WebSocket Testsuite Report
Autobahn WebSocket

websock server - Case 5.14 : Pass - 1 ms @ 2024-11-28T05:30:50.294Z

Case Description

Send unfragmented Text Message after Continuation Frame with FIN = false, 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)



Opening Handshake

GET /ws HTTP/1.1
User-Agent: AutobahnTestSuite/0.8.2-0.10.9
Host: 127.0.0.1:8888
Upgrade: WebSocket
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: +4OfkPpzcjpNIXrTR4fo9w==
Sec-WebSocket-Version: 13
HTTP/1.1 101 Switching Protocols
Date: Thu, 28 Nov 2024 05:30:50 GMT
Upgrade: websocket
Connection: Upgrade
Sec-Websocket-Accept: H1TrUZz9mIaGNPMGJv6hh+OEtjg=


Closing Behavior

KeyValueDescription
isServerFalseTrue, iff I (the fuzzer) am a server, and the peer is a client.
closedByMeFalseTrue, iff I have initiated closing handshake (that is, did send close first).
failedByMeFalseTrue, 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.
droppedByMeFalseTrue, iff I dropped the TCP connection.
wasCleanFalseTrue, iff full WebSocket closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReasonpeer dropped the TCP connection without previous WebSocket closing handshakeWhen wasClean == False, the reason what happened.
wasServerConnectionDropTimeoutFalseWhen we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeoutFalseWhen performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeoutFalseWhen we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCodeNoneThe close code I sent in close frame (if any).
localCloseReasonNoneThe close reason I sent in close frame (if any).
remoteCloseCodeNoneThe close code the peer sent me in close frame (if any).
remoteCloseReasonNoneThe close reason the peer sent me in close frame (if any).


Wire Statistics

Octets Received by Chop Size

Chop SizeCountOctets
1661166
Total1166

Octets Transmitted by Chop Size

Chop SizeCountOctets
188
2421242
Total9250

Frames Received by Opcode

OpcodeCount
Total0

Frames Transmitted by Opcode

OpcodeCount
01
11
Total2


Wire Log

000 TX OCTETS: 474554202f777320485454502f312e310d0a557365722d4167656e743a204175746f6261686e5465737453756974652f302e
               382e322d302e31302e390d0a486f ...
001 RX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a446174653a205468752c203238204e6f
               7620323032342030353a33303a35 ...
002 TX FRAME : OPCODE=0, FIN=False, RSV=0, PAYLOAD-LEN=24, MASK=fbd80514, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
               non-continuation payload
003 TX OCTETS: 00
004 TX FRAME : OPCODE=1, FIN=True, RSV=0, PAYLOAD-LEN=13, MASK=813cff56, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=1, SYNC=False
               Hello, world!
005 FAIL CONNECTION AFTER 1.000000 sec
006 TX OCTETS: 98
007 TX OCTETS: fb
008 TX OCTETS: d8
009 TX OCTETS: 05
010 TX OCTETS: 14
011 TX OCTETS: 95
012 TX OCTETS: b7
013 TCP DROPPED BY PEER