3 ms·
And how about putting an informative tooltip on google's pages? They could use Javascript to query a test server, which responds with the correct headers. If th
by MayeulC 8y ago
And how about putting an informative tooltip on google's pages?
They could use Javascript to query a test server, which responds with the correct headers. If the answer doesn't get trough, print a message.
Hopefully someone will notice and bring it up with the IT or ISP, especially if the message says to do so, and that Google/internet could stop working in the future.
Actually,get more popular sites to do it, like Facebook, Twitter, Apple and Microsoft (heck, they could do it as a part of the operating system): if a lot of websites say it, users will tend to think that something is wrong on their end.
This was surely already brought up as a solution, so I wonder what the catch was, if any?
Since this would be browser-independent, the browser wouldn't get blamed, and if it's only a mild inconvenience, it shouldn't bother people that much (they have been using the web despite more invasive cookie notices). I would expect it to allow a critical number of non conformant devices to be quickly disabled as a result.
- CapacitorSet 8y ago>They could use Javascript to query a test server, which responds with the correct headers. As far as I know, Javascript doesn't have low-level access to connections, not enough to run even a stub TLS 1.3 implementation.
- MayeulC 8y agoI was more thinking about querying something like testtls.google.com, that would analyze the results server-side (this might require an extra round-trip), and return them to be displayed.