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:

<!--
	IMPORTANT INFORMATION:

	Sites, developed by the public, created on the Enjin Network have the ability to force
	HTTP or HTTPS themselves. If they enable HTTPS, the site will automatically force a
	HTTPS connection. You cannot add a rule to force HTTPS for sites that specifically
	request to force the HTTP protocol, doing so will cause a redirect loop
	(between the HTTP and HTTPS protocols) to occur.

	This functionality may be altered in the near future to ensure all sites use HTTPS and proxy
	insecure material (such as scripts, stylesheets and images) through a HTTPS-enabled proxy.
--><ruleset name="Enjin" platform="mixedcontent">
	<!-- Enjin Network -->
	<target host="enjin.com"/>
	<target host="www.enjin.com"/>
	<target host="support.enjin.com"/>
	<target host="id.enjin.com"/>
	<target host="api.enjin.com"/>

	<!--
		CDN Rules:
			- CDNs serve mismatching certificates. Thus, should use a different URL to properly support HTTPS.
	-->
	<target host="assets-cloud.enjin.com"/>
	<target host="files-cloud.enjin.com"/>
	<target host="images-cloud.enjin.com"/>
	<target host="assets.enjin.com"/>
	<target host="files.enjin.com"/>
	<target host="images.enjin.com"/>

	<test url="http://assets-cloud.enjin.com/ext/test.html"/>
	<test url="http://assets.enjin.com/ext/test.html"/>
	<test url="http://files-cloud.enjin.com/ext/test.html"/>
	<test url="http://files.enjin.com/ext/test.html"/>
	<test url="http://images-cloud.enjin.com/ext/test.html"/>
	<test url="http://images.enjin.com/ext/test.html"/>

	<rule from="^http://(files|assets|images)\.enjin\.com/" to="https://s3.amazonaws.com/$1.enjin.com/"/>
	<rule from="^http:" to="https:"/>
</ruleset>

Enjin.xml    File a bug

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

<!--
	IMPORTANT INFORMATION:

	Sites, developed by the public, created on the Enjin Network have the ability to force
	HTTP or HTTPS themselves. If they enable HTTPS, the site will automatically force a
	HTTPS connection. You cannot add a rule to force HTTPS for sites that specifically
	request to force the HTTP protocol, doing so will cause a redirect loop
	(between the HTTP and HTTPS protocols) to occur.

	This functionality may be altered in the near future to ensure all sites use HTTPS and proxy
	insecure material (such as scripts, stylesheets and images) through a HTTPS-enabled proxy.
--><ruleset name="Enjin" platform="mixedcontent">
	<!-- Enjin Network -->
	<target host="enjin.com"/>
	<target host="www.enjin.com"/>
	<target host="support.enjin.com"/>
	<target host="id.enjin.com"/>
	<target host="api.enjin.com"/>

	<!--
		CDN Rules:
			- CDNs serve mismatching certificates. Thus, should use a different URL to properly support HTTPS.
	-->
	<target host="assets-cloud.enjin.com"/>
	<target host="files-cloud.enjin.com"/>
	<target host="images-cloud.enjin.com"/>
	<target host="assets.enjin.com"/>
	<target host="files.enjin.com"/>
	<target host="images.enjin.com"/>

	<test url="http://assets-cloud.enjin.com/ext/test.html"/>
	<test url="http://assets.enjin.com/ext/test.html"/>
	<test url="http://files-cloud.enjin.com/ext/test.html"/>
	<test url="http://files.enjin.com/ext/test.html"/>
	<test url="http://images-cloud.enjin.com/ext/test.html"/>
	<test url="http://images.enjin.com/ext/test.html"/>

	<rule from="^http://(files|assets|images)\.enjin\.com/" to="https://s3.amazonaws.com/$1.enjin.com/"/>
	<rule from="^http:" to="https:"/>
</ruleset>

Enjin.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 f49a3ab6 2019-12-11 04:21:56 +0000;