On Thu, Feb 22, 2018 at 11:02:59AM +0800, [email protected] wrote:
Hmmm...If that'd be the case, is it well worth considering "NoScript" and "HTTPS Everywhere" as part of the default extensions suite?
I stopped using HTTPS Everywhere because it would prevented me from using certain sites, and it became too tedious to use: http://foo/ and https://foo/ are different URLs and there's no reason they'd have the same content; HTTPS Everywhere wasn't smart enough to check whether the pages served were intended to represent the same resource (through any method beyond schema-free string matching).
Unless the plug-in has found a better way of dealing with this, I think the default install of a Web browser should try to load the location the user specified, and the extension should be avoided. (This falls under the same umbrella of "not where I said" as automatically searching Google, Bing, or another search engines in stock configurations when the browser fails to resolve a domain.)
-- Matthew Wronka <http://matt.wronka.org/><sip:[email protected]><mailto:""@無.com> pgp key: http://matt.wronka.org/pgp/pgp.key Short PGP FAQ: http://www.pgp.net/pgpnet/pgp-faq/pgp-faq-general-questions.html -- http://gnuzilla.gnu.org
