> (Note: my website shall be accessible only by non-Chrome web browsers, it is not accessible to Chrome-based clients due to its hardcoded client-side HTTP/2 mandate ignoring and overriding my TLS server’s must have HTTP/1.2-only, ChaCha-only. Chrome is broke, remains my assertion).
I guess everyone needs a hobby lmao. Also what is exactly the problem ? On wireshark I see chrome sending hello with TLS1.2/1.3 and TLS_CHACHA20_POLY1305_SHA256 (0x1303) then getting rejected https://imgur.com/a/HjZormT
Correct. TLSv1.2 is getting obsoleted due to several CVEs, so block that.
I would be talking about my server mandating HTTP/1.3 over Chrome mandating HTTP/2.0 of which Chrome does poorly in concise error messaging. Since my server decides, it fails.
On an unrelated note, stick with TLS v1.3 whenever you can.
I suggest you fix the HTTP TLS-less version of the site, so that chromium browsers may access the plaintext version.
Currently I get a 404 Not Found for the linked HTML file when connecting via plaintext.
TLS only complicated things (: I don't really need to verify the website integrity and privacy when reading an article from a HN commenter I do not know (: Maybe it's only about cosmetics -- a green padlock is more pleasing than a red triangle.
I guess everyone needs a hobby lmao. Also what is exactly the problem ? On wireshark I see chrome sending hello with TLS1.2/1.3 and TLS_CHACHA20_POLY1305_SHA256 (0x1303) then getting rejected https://imgur.com/a/HjZormT