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:

<!--
Mismatched:
demo.101weiqi.com
--><ruleset name="101weiqi.com">
<!--
101weiqi.com use the http://www.qiniu.com/ cloud for some files.
However, they do not support https directly and make some mixedcontent problem.
Lucky, the host owner has binded domain, so we can redirect them to the main host, which support https.
-->
<target host="7j1yxi.com1.z0.glb.clouddn.com"/>
<rule from="^http://7j1yxi\.com1\.z0\.glb\.clouddn\.com/" to="https://www.101weiqi.com/"/>
<test url="http://7j1yxi.com1.z0.glb.clouddn.com/file/head/2015/7/23/4882_56993_51_2.png"/>
<target host="101weiqi.com"/>
<target host="www.101weiqi.com"/>
<test url="http://www.101weiqi.com/login"/>
<rule from="^http:" to="https:"/>
</ruleset>

The release branch contains the following rules that are enabled by default:

<!--
Mismatched:
demo.101weiqi.com
--><ruleset name="101weiqi.com">
<!--
101weiqi.com use the http://www.qiniu.com/ cloud for some files.
However, they do not support https directly and make some mixedcontent problem.
Lucky, the host owner has binded domain, so we can redirect them to the main host, which support https.
-->
<target host="7j1yxi.com1.z0.glb.clouddn.com"/>
<rule from="^http://7j1yxi\.com1\.z0\.glb\.clouddn\.com/" to="https://www.101weiqi.com/"/>
<test url="http://7j1yxi.com1.z0.glb.clouddn.com/file/head/2015/7/23/4882_56993_51_2.png"/>
<target host="101weiqi.com"/>
<target host="www.101weiqi.com"/>
<test url="http://www.101weiqi.com/login"/>
<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.