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 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://visit.mashery.com/ => https://visit.mashery.com/: (60, 'SSL certificate problem: certificate has expired') CDN buckets: - s3.amazonaws.com/content.developer.mashery.com/ Nonfunctional subdomains: - blog (Dropped) ^mashery.com: Refused Partially covered hosts in *mashery.com: - dev * - developer * - support * * Some pages redirect to http Fully covered hosts in *mashery.com: - (www.)? (^ → www) - demo1 - content.developer (→ s3.amazonaws.com) - secure - visit Insecure cookies are set for these hosts: - visit.mashery.com --><ruleset name="Mashery.com (partial)" default_off="failed ruleset test"> <!-- Direct rewrites: --> <target host="demo1.mashery.com"/> <target host="dev.mashery.com"/> <target host="developer.mashery.com"/> <target host="secure.mashery.com"/> <target host="support.mashery.com"/> <target host="visit.mashery.com"/> <target host="www.mashery.com"/> <!-- Complications: --> <target host="mashery.com"/> <target host="content.developer.mashery.com"/> <!-- At least the home page 301s to http. Exceptions: --> <exclusion pattern="^http://(?:dev|developer|support)\.mashery\.com/(?!files/|public/)"/> <!-- +ve: --> <test url="http://dev.mashery.com/apis"/> <test url="http://developer.mashery.com/apis"/> <test url="http://support.mashery.com/GettingStarted"/> <!-- -ve: --> <test url="http://dev.mashery.com/public/Mashery/styles/Iodocs/prettify.css"/> <test url="http://developer.mashery.com/files/developernetwork-theme1.79.css"/> <test url="http://developer.mashery.com/public/Mashery/styles/print-default.css"/> <test url="http://support.mashery.com/public/Mashery/images/masherysupport/local.gif"/> <!-- Not secured by server: --> <!--securecookie host="^visit\.mashery\.com$" name="^BIGipServer[\w-]+$" /--> <securecookie host="^(?:secure|visit)\.mashery\.com$" name=".+"/> <!-- Redirect keeps forward slash, path, and args: --> <rule from="^http://mashery\.com/" to="https://www.mashery.com/"/> <rule from="^http://content\.developer\.mashery\.com/" to="https://s3.amazonaws.com/content.developer.mashery.com/"/> <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.