Embedded content loaded from third-party domains (for example, YouTube, Google Analytics, ad networks, or CDNs) may also be affected. You can test this by loading the web page in question in a browser with HTTPS Everywhere installed and pulling down the HTTPS Everywhere rules menu. This will show a list of HTTPS Everywhere rules that were applied as the page was loaded, including rules that might have affected embedded content from other domains.
The stable (as yet unreleased) branch contains the following rule that is disabled by default (so very few users' browsing is likely to be affected by their action):
<!-- Disabled by https-everywhere-checker because: Fetch error: http://webadvisor.uchastings.edu/ => https://webadvisor.uchastings.edu/: (60, 'SSL certificate problem: unable to get local issuer certificate') For rules causing false/broken MCB, see UC_Hastings.edu-falsemixed.xml. For problematic rules, see UC_Hastings.edu-problematic.xml. Problematic subdomains: - (www.)? ¹ - events ² - journals ¹ ² - library ¹ ² ¹ Server sends no certificate chain, see https://whatsmychaincert.com ² Mixed css These altnames don't exist: - www.events.uchastings.edu Insecure cookies are set for these hosts: - events.uchastings.edu Mixed content: - css, on: - events, journals from fonts.googleapis.com ¹ - events from hws.uchastings.edu ¹ - journals, library from (www.)?uchastings.edu ² - Images, on (www.)?, hws, journals, library from (www.)?uchastings.edu ² - favicon on journals, library from (www.)?uchastings.edu ² ¹ Secured by us ² Rule disabled by default <= missing certificate chain --><ruleset name="UC Hastings.edu (partial)" default_off="failed ruleset test"> <!-- Direct rewrites: --> <!--target host="uchastings.edu" /--> <target host="cio2.uchastings.edu"/> <!--target host="events.uchastings.edu" /--> <target host="hws.uchastings.edu"/> <!--target host="journals.uchastings.edu" /--> <!--target host="library.uchastings.edu" /--> <target host="webadvisor.uchastings.edu"/> <!--target host="www.uchastings.edu" /--> <!-- Not secured by server: --> <!--securecookie host="^events\.uchastings\.edu$" name="^ASP\.NET_SessionId$" /--> <!--securecookie host="^events\.uchastings\.edu$" name=".+" /--> <rule from="^http:" to="https:"/> </ruleset>
The release branch contains the following rules that are disabled by default (so very few users' browsing is likely to be affected by their action):
<!-- Disabled by https-everywhere-checker because: Fetch error: http://webadvisor.uchastings.edu/ => https://webadvisor.uchastings.edu/: (60, 'SSL certificate problem: unable to get local issuer certificate') For rules causing false/broken MCB, see UC_Hastings.edu-falsemixed.xml. For problematic rules, see UC_Hastings.edu-problematic.xml. Problematic subdomains: - (www.)? ¹ - events ² - journals ¹ ² - library ¹ ² ¹ Server sends no certificate chain, see https://whatsmychaincert.com ² Mixed css These altnames don't exist: - www.events.uchastings.edu Insecure cookies are set for these hosts: - events.uchastings.edu Mixed content: - css, on: - events, journals from fonts.googleapis.com ¹ - events from hws.uchastings.edu ¹ - journals, library from (www.)?uchastings.edu ² - Images, on (www.)?, hws, journals, library from (www.)?uchastings.edu ² - favicon on journals, library from (www.)?uchastings.edu ² ¹ Secured by us ² Rule disabled by default <= missing certificate chain --><ruleset name="UC Hastings.edu (partial)" default_off="failed ruleset test"> <!-- Direct rewrites: --> <!--target host="uchastings.edu" /--> <target host="cio2.uchastings.edu"/> <!--target host="events.uchastings.edu" /--> <target host="hws.uchastings.edu"/> <!--target host="journals.uchastings.edu" /--> <!--target host="library.uchastings.edu" /--> <target host="webadvisor.uchastings.edu"/> <!--target host="www.uchastings.edu" /--> <!-- Not secured by server: --> <!--securecookie host="^events\.uchastings\.edu$" name="^ASP\.NET_SessionId$" /--> <!--securecookie host="^events\.uchastings\.edu$" name=".+" /--> <rule from="^http:" to="https:"/> </ruleset>
The HTTPS Everywhere developers welcome corrections and updates to rules. Please see our developer information and documentation of the ruleset format. If filing a bug in the Tor Project's Trac bug tracker, you can use the shared username and password cypherpunks / writecode; please ensure that the bug is marked as applying to HTTPS Everywhere.
Information current as of:
current release 79252541 2021-07-13 13:19:11 -0700;
next release 17d61a00 2022-05-25 04:06:39 +0000;
current release 79252541 2021-07-13 13:19:11 -0700;
next release 17d61a00 2022-05-25 04:06:39 +0000;