Precisely. Your Chrome must be broken and arguably intentionally so.
You will find that my web server does not offer any AES algorithm option in which for a Chrome web client to currently get twisted into a knot over.
Oppositely, you will find nearly all other web clients able to handle these non-AES algorithm of TLSv1.3 server option quite well.
Web clients like Aloha, Brave, curl, DuckDuckGo, Edge, Firefox (any), Firefox Focus (iOS), LibreFox, links (CLI), Lynx, OnionBrowser (iOS), Opera, Orion (iOS), Safari, SeaMonkey, TorBrowser, Vivaldi, and wget all work well without any AES algorithm in TLS v1.3.
This is my website’s way of doing things that the TLS v1.3 spec allows us to do.
You will find that my web server does not offer any AES algorithm option in which for a Chrome web client to currently get twisted into a knot over.
Oppositely, you will find nearly all other web clients able to handle these non-AES algorithm of TLSv1.3 server option quite well.
Web clients like Aloha, Brave, curl, DuckDuckGo, Edge, Firefox (any), Firefox Focus (iOS), LibreFox, links (CLI), Lynx, OnionBrowser (iOS), Opera, Orion (iOS), Safari, SeaMonkey, TorBrowser, Vivaldi, and wget all work well without any AES algorithm in TLS v1.3.
This is my website’s way of doing things that the TLS v1.3 spec allows us to do.
And I play with maximum cyber security.