Raymond Hill 91e702cebb Enable CNAME uncloaking by default ... Advanced setting `cnameAliasList` has been removed. New advanced settings: cnameUncloak: Boolean Default value: true Description: Whether to CNAME-uncloak hostnames. cnameIgnoreExceptions: Boolean Default value: true Description: Whether to bypass the uncloaking of network requests which were excepted by filters/rules. This is necessary so as to avoid undue breakage by having exception filters being rendered useless as a result of CNAME-uncloaking. For example, `google-analytics.com` uncloaks to `www-google-analytics.l.google.com` and both hostnames appear in Peter Lowe's list, which means exception filters for `google-analytics.com` (to fix site breakage) would be rendered useless as the uncloaking would cause the network request to be ultimately blocked.		2019-12-01 12:05:49 -05:00
..
manifest.json	Add ability to uncloak CNAME records	2019-11-19 12:05:33 -05:00
vapi-usercss.js	guard against future instances of issue fixed in #3721	2018-05-03 09:55:36 -04:00
vapi-webrequest.js	Enable CNAME uncloaking by default	2019-12-01 12:05:49 -05:00
webext.js	Work toward modernizing code base: promisification	2019-09-16 09:45:17 -04:00