https-everywhere-checker
https-everywhere-checker copied to clipboard
hiviah
Obsolete, upkept version at EFF
[This Travis build](https://travis-ci.org/EFForg/https-everywhere/builds/99711962), called from https://github.com/EFForg/https-everywhere/pull/3726, triggers an error which shouldn't really be triggered.
This one is inspired by https://github.com/EFForg/https-everywhere/pull/4280#issuecomment-192921081 and https://github.com/EFForg/https-everywhere/pull/2585 I figured I'd try to run the checker against [a ruleset](https://github.com/fuglede/https-everywhere/blob/drugcom-test/src/chrome/content/rules/Drugcom.de.xml) which would cause problems in the wild, and which I would...
If a test URL is included in a ruleset, but that test URL is not covered by any target host, the checker will not flag an error. See, for instance,...
Specifically, in HTTPS Everywhere, right-wildcards don't match arbitrarily deep (unlike left wildcards, which do). Specifically, google.\* will match google.com but not google.com.au. However, I think https-everywhere-checker does match arbitrarily deep....
Right now the checker fetches both the HTTP version and the rewritten HTTPS version of a URL, and fails if either one fails. There are a small number of cases...
For ruleset coverage testing, we currently check that each rule and exclusion has a number of covering test URLs. We should add logic that checks that each target host has...