You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
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 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.
Activity
luixxiul commentedon Jul 29, 2016
I get mixed content warnings because of
http://stat100.ameba.jp, which however should be redirected to https thanks to this. Not sure why?luixxiul commentedon Jul 29, 2016
This too: https://official.ameba.jp/
luixxiul commentedon Jul 29, 2016
By the way if I directly get the blocked resource from URL bar, they are redirected to https.
jbrowngithubuser commentedon Jul 30, 2016
Chrome and Firefox block active mixed content before HTTPS-Everywhere has a chance to rewrite the URLS to https://
See https://www.eff.org/https-everywhere/rulesets