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 enabled by default:
<!-- This domain has wildcard certificate and DNS records. Active mixed content: - (*.)?eyny.com, from www.facebook.com - https://eyny.com/thread-9439862-1-1.html - https://eyny.com/thread-10612510-1-1.html Bad redirect: - eyny.com, equivalent to eyny.com/index.php - www.eyny.com, equivalent to www.eyny.com/index.php --><ruleset name="Eyny.com" platform="mixedcontent"> <target host="eyny.com"/> <target host="*.eyny.com"/> <test url="http://www.eyny.com/"/> <test url="http://blog.eyny.com/"/> <test url="http://bt.eyny.com/"/> <test url="http://video.eyny.com/"/> <rule from="^http://(www\.)?eyny\.com/$" to="https://$1eyny.com/index.php"/> <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.