Quoting from the recently-updated rulesets page: "Some rulesets may trigger active mixed content (i.e. scripts loaded over HTTP instead of HTTPS). This type of mixed content is blocked in both Chrome <https://trac.torproject.org/projects/tor/ticket/6975> and Firefox, before HTTPS Everywhere has a chance to rewrite the URLs to an HTTPS version. This generally breaks the site. However, the Tor Browser doesn't block mixed content, in order to allow HTTPS Everywhere to try and rewrite the URLs to an HTTPS version.
To enable a rule only on platforms that allow mixed content (currently only the Tor Browser), you can add a platform="mixedcontent" attribute to the ruleset element." https://www.eff.org/https-everywhere/rulesets#mixed-content On 04/16/2015 09:44 AM, Alexander Buchner wrote: > I found some rules that have the tag > platform="mixedcontent" > > Are there rulesets disabled because of these tags? > And if yes: Is this necessary? > _______________________________________________ > HTTPS-Everywhere mailing list > [email protected] > https://lists.eff.org/mailman/listinfo/https-everywhere >
_______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
