https-everywhere-rules

Author	SHA1	Message	Date
vi	c26afe01cf	Don't admit package-wise parameterisation of rulesets. As 'a6f28e07a1edc8f62f3dfaf7965b3a818c2f4a7f' showed, there may be breaking changes in the structure of rulesets between releases. I don't intend to verify that every pair in the product works (is there reason to be interested in any other than the latest?), so let's not acommodate any more than one.	2015-11-08 00:53:35 +08:00
vi	e3c171b67e	Prepare to assimilate https-everywhere-rules-raw.	2015-11-04 21:57:59 +08:00
vi	6d12745fc9	Interface change for consistency: rewriteURL is idempotent on addresses with no matching rules.	2014-08-24 23:57:55 +08:00
vi	5af781291f	Correct pipeline semantics.	2014-08-24 12:57:35 +08:00
vi	49be7aa1a0	Use more structured URI representation; targets match only hosts. This resolves #2.	2014-08-11 03:32:51 +08:00
vi	5060883c5a	Broken domain logic.	2014-08-10 07:16:57 +08:00
vi	f78421e09f	Incomplete parser for HTTPS Everywhere rulesets.	2014-08-10 04:23:41 +08:00