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 release branch contains the following rules that are enabled by default:

		http redirects to
		https 404's.
		https redirects to
		http(s) and 404s
		http redirects to https
		/play/ subfolder breaks because of ajax and js that have to load from http (all links to this directory already downgrade)
		Most links specify http in the url.
--><ruleset name="">
	<target host=""/>
	<target host=""/>
	<target host=""/>

	<exclusion pattern="^http://(www\.)?byond\.com/play/"/>
		<test url=""/>
		<test url=""/>

	<rule from="^http://byond\.com/" to=""/>

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

</ruleset>    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 ff5b4642b 2019-06-27 14:21:20 -0700;
next release c0a0e49cd 2019-10-16 02:46:21 +0300;