Also, regarding how to prevent similar bugs in the future: I've already updated our ruleset validator to catch this case (bad regexp in securecookie name field). I also have a pull request open to put a try/catch around processing each ruleset: https://github.com/EFForg/https-everywhere/pull/2229.
I'd very much like to add automated Chrome testing, similar to our Firefox automated test: Start up a Chrome profile with the extension loaded, open a sample URL, and verify that it got rewritten to HTTPS. Some of the groundwork is in run-chromium.sh, but I'm not sure how to proceed with the rest of the test. If you have some ideas, please contribute! Thanks, Jacob _______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
