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:

<!--
	Other Weibo coverage:
		Weibo.cn.xml
		WeiboPay.com.xml

	Invalid certificate:
		static.book.weibo.com
		service.weibo.com

	MCB:
		chart.weibo.com		( Too many redirects )
		game.weibo.com
		vgirl.weibo.com

	not enough values to unpack:
		captcha.weibo.com	https://travis-ci.org/EFForg/https-everywhere/jobs/578760969#L599

	Redirect to http:
		sg2.game.weibo.com
		hr.weibo.com
		manhua.weibo.com

	Timeout:
		yahoo.tw.weibo.com
--><ruleset name="Weibo.com">
	<target host="weibo.com"/>
	<target host="www.weibo.com"/>
	<target host="api.weibo.com"/>
		<exclusion pattern="http://api\.weibo\.com/chat/"/>
		<test url="http://api.weibo.com/chat/#/main"/>
	<target host="rm.api.weibo.com"/>
		<test url="http://rm.api.weibo.com/2/remind/unread_count.json?source=1654744673"/>
	<target host="upload.api.weibo.com"/>
		<test url="http://upload.api.weibo.com/2/statuses/upload.json"/>
	<target host="app.weibo.com"/>
	<target host="book.weibo.com"/>
	<target host="e.weibo.com"/>
	<target host="help.weibo.com"/>
	<target host="open.weibo.com"/>
	<target host="passport.weibo.com"/>
	<target host="s.weibo.com"/>
	<target host="security.weibo.com"/>
		<test url="http://security.weibo.com/app/js/v1/apps/account/jQuery1.7.1.js"/>
	<target host="vdisk.weibo.com"/>
	<target host="video.weibo.com"/>
		<test url="http://video.weibo.com/show?fid=1034:4312779088411554"/>
	<target host="widget.weibo.com"/>

	<securecookie host=".+" name=".+"/>

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

Weibo.com.xml    File a bug

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

<!--
	Other Weibo coverage:
		Weibo.cn.xml
		WeiboPay.com.xml

	Insecure cookies are set for these domains and hosts:
		.weibo.com
		game.weibo.com
		sg2.game.weibo.com
		yahoo.tw.weibo.com

	Redirect to http:
		vdisk.weibo.com

	MCB:
		app.weibo.com
		chart.weibo.com		( Too many redirects )
		game.weibo.com
		manhua.weibo.com
		vgirl.weibo.com

	Invalid certificate:
		www.weibo.com	( Mismatched by some strange CDNs. Equal to ^ )
		book.weibo.com
		static.book.weibo.com
		caipiao.weibo.com
		sg2.game.weibo.com
		hr.weibo.com
		rm2015.tv.weibo.com
		service.weibo.com
		x.weibo.com
--><ruleset name="Weibo.com">
	<target host="weibo.com"/>
	<target host="www.weibo.com"/>
	<target host="api.weibo.com"/>
		<exclusion pattern="http://api\.weibo\.com/chat/"/>
		<test url="http://api.weibo.com/chat/#/main"/>
	<target host="rm.api.weibo.com"/>
		<test url="http://rm.api.weibo.com/2/remind/unread_count.json?source=1654744673"/>
	<target host="upload.api.weibo.com"/>
		<test url="http://upload.api.weibo.com/2/statuses/upload.json"/>
	<target host="captcha.weibo.com"/>
		<test url="http://captcha.weibo.com/static/js/patternLock.min.js"/>
	<target host="e.weibo.com"/>
	<target host="gouwu.weibo.com"/>
	<target host="help.weibo.com"/>
	<target host="open.weibo.com"/>
	<target host="passport.weibo.com"/>
	<target host="s.weibo.com"/>
	<target host="security.weibo.com"/>
		<test url="http://security.weibo.com/app/js/v1/apps/account/jQuery1.7.1.js"/>
	<target host="yahoo.tw.weibo.com"/>
	<target host="video.weibo.com"/>
		<test url="http://video.weibo.com/show?fid=1034:4312779088411554"/>
	<target host="widget.weibo.com"/>

	<securecookie host=".+" name=".+"/>

	<rule from="^http://www\.weibo\.com/" to="https://weibo.com/"/>

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

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