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:
<!-- For other Santander coverage, see Santander.co.uk.xml. ^santanderbillpayment.co.uk: Dropped STS header includes includeSubdomains Insecure cookies are set for these hosts: - www.santanderbillpayment.co.uk --><ruleset name="Santander BillPayment.co.uk"> <!-- Direct rewrites: --> <target host="*.santanderbillpayment.co.uk"/> <!-- Complications: --> <target host="santanderbillpayment.co.uk"/> <test url="http://www.santanderbillpayment.co.uk/"/> <!-- Not secured by server: --> <!--securecookie host="^www\.santanderbillpayment\.co\.uk$" name="^BIGipServer" /--> <securecookie host=".+" name=".+"/> <!-- Redirect drops path but not args: --> <rule from="^http://santanderbillpayment\.co\.uk/+\??$" to="https://www.santanderbillpayment.co.uk/"/> <test url="http://santanderbillpayment.co.uk/?"/> <rule from="^http://santanderbillpayment\.co\.uk/[^?]*" to="https://www.santanderbillpayment.co.uk/"/> <test url="http://santanderbillpayment.co.uk/default.aspx"/> <test url="http://santanderbillpayment.co.uk/index.htm"/> <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.