HTTPS Everywhere Atlas

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:

<!--
	For problematic rules, see YellowPages.ca-problematic.xml.


	Problematic subdomains:

		- (www.) *
		- yahoo.aws *

	* Works; mismatched, CN: secure.yellowpages.ca


	Mixed content:

		- css on (www.) and yahoo.aws from cdn.cb.yp.ca *

	Unsecurable <= 400

--><ruleset name="YellowPages.ca (partial)">

	<target host="secure.yellowpages.ca"/>


	<!--	Not secured by server:
					-->
	<!--securecookie host="^secure\.yellowpages\.ca$" name="^TS01[\da-f]{6}$" /-->
	<!--securecookie host="^\.yellowpages\.ca$" name="^psid_ypca$" /-->

	<!--	psid_ypca appears to identify clients' pages and appears not to
		be used on secure.
			So, if we handle it whenever we can - that is, whenever
		the browser navigates to any applicable domain over tls, we
		shouldn't cause any problems. In this way, Secure is set when
		users fetch problematic domains over tls without enabling the
		problematic ruleset.
					-->
	<securecookie host="^\.yellowpages\.ca$" name="^psid_ypca$"/>
	<securecookie host="^secure\.yellowpages\.ca$" name=".+"/>


	<rule from="^http:" to="https:"/>

</ruleset>

YellowPages.ca.xml    File a bug

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

<!--
	For problematic rules, see YellowPages.ca-problematic.xml.


	Problematic subdomains:

		- (www.) *
		- yahoo.aws *

	* Works; mismatched, CN: secure.yellowpages.ca


	Mixed content:

		- css on (www.) and yahoo.aws from cdn.cb.yp.ca *

	Unsecurable <= 400

--><ruleset name="YellowPages.ca (partial)">

	<target host="secure.yellowpages.ca"/>


	<!--	Not secured by server:
					-->
	<!--securecookie host="^secure\.yellowpages\.ca$" name="^TS01[\da-f]{6}$" /-->
	<!--securecookie host="^\.yellowpages\.ca$" name="^psid_ypca$" /-->

	<!--	psid_ypca appears to identify clients' pages and appears not to
		be used on secure.
			So, if we handle it whenever we can - that is, whenever
		the browser navigates to any applicable domain over tls, we
		shouldn't cause any problems. In this way, Secure is set when
		users fetch problematic domains over tls without enabling the
		problematic ruleset.
					-->
	<securecookie host="^\.yellowpages\.ca$" name="^psid_ypca$"/>
	<securecookie host="^secure\.yellowpages\.ca$" name=".+"/>


	<rule from="^http:" to="https:"/>

</ruleset>

YellowPages.ca.xml    File a bug

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.

Information current as of:


current release a9c79875 2019-11-07 15:00:59 -0800;
next release 28fe0feb 2019-12-10 04:21:51 +0000;