[HTTPS-Everywhere] repository for just the rulesets?

Jacob Hoffman-Andrews jsha at eff.org
Fri Jan 30 10:14:29 PST 2015


> heproxy[0] is really in the nascent stages -- I've spent about 4 hours
total on it, but it's looking pretty promising already.
https://github.com/apg/heproxy Ideally, this sort of functionality could
be included in something like privoxy[1], using the same ruleset files
that are maintained in the HTTPS Everywhere project. Of course, for this
to happen, I think it'd be ideal if the rulesets were actually a
separate project.

This is really neat, thanks for sending! Currently I don't have plans to
break out the rulesets into a separate repo, since there are other
maintainability changes that I think are more important. It's a
possibility in the future, but in the meantime I think your approach works.

You talk about tracking a subdirectory of the https-everywhere repo. Why
not instead just track the whole repo and have your proxy's input path
point at src/chrome/content/rules?

Also, you might be interested in a similar thing I wrote in Node, aimed
at helping webmasters rewrite their pages to point to HTTPS resources:
https://github.com/EFForg/https-everywhere/pull/81


More information about the HTTPS-Everywhere mailing list