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 enabled by default:
<!-- CDN buckets: - files.zimbra.com.s3.amazonaws.com - files2.zimbra.com.edgesuite.net - a1843.g.akamai.net Problematic domains: - zimbra.com subdomains: - files (amazonws) - files2 (works, akamai) - (www.)zimbrablog.com (works; mismatched, CN: *.zimbra.com) Fully covered domains: - *.zimbra.com: - (www.) - blog - files * - files2 * - gallery - help - (www.)zimbrablog.com (→ blog.zimbra.com) * → s3.amazonaws.com/files.zimbra.com/ Mixed content: - Scripts: - On blog from www.google.com * - On help from www.google.com * - On www from www * - On www from www.google.com * - css: - On blog from blog * - On blog from www.google.com * - On www from www * - On www from www.google.com * - Images, on www from: - www * - feeds2.feedburner.com ** - Web bug on www from munchkin.marketo.net * * Secured by us ** Unsecurable, doesn't trip MCB anyway NB: We secure all resources, and thus platform should be removed with Ffx 24. --><ruleset name="Zimbra (false MCB)" platform="mixedcontent"> <target host="zimbra.com"/> <target host="*.zimbra.com"/> <target host="zimbrablog.com"/> <target host="www.zimbrablog.com"/> <!--securecookie host="^\.zimbra\.com$" name="^(_mkto_trk|optimizely\w+|__utm\w)$" /--> <securecookie host="^(?:.*\.)?zimbra\.com$" name=".+"/> <rule from="^http://files2?\.zimbra\.com/" to="https://s3.amazonaws.com/files.zimbra.com/"/> <rule from="^http://([^/:@\.]+\.)?zimbra\.com/" to="https://$1zimbra.com/"/> <rule from="^http://(?:www\.)?zimbrablog\.com/" to="https://blog.zimbra.com/"/> </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.