<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif;font-size:small"><div class="gmail_default">Hi.</div><div class="gmail_default"><br></div><div class="gmail_default">“Add a rule for this site” doesn’t seem to work in version 2015.7.15.</div><div class="gmail_default"><br></div><div class="gmail_default">Thanks.</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-07-15 19:53 GMT+02:00 Jacob Hoffman-Andrews <span dir="ltr"><<a href="mailto:jsha@eff.org" target="_blank">jsha@eff.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Also, regarding how to prevent similar bugs in the future:<br>
<br>
I've already updated our ruleset validator to catch this case (bad<br>
regexp in securecookie name field). I also have a pull request open to<br>
put a try/catch around processing each ruleset:<br>
<a href="https://github.com/EFForg/https-everywhere/pull/2229" rel="noreferrer" target="_blank">https://github.com/EFForg/https-everywhere/pull/2229</a>.<br>
<br>
I'd very much like to add automated Chrome testing, similar to our<br>
Firefox automated test: Start up a Chrome profile with the extension<br>
loaded, open a sample URL, and verify that it got rewritten to HTTPS.<br>
Some of the groundwork is in run-chromium.sh, but I'm not sure how to<br>
proceed with the rest of the test. If you have some ideas, please<br>
contribute!<br>
<br>
Thanks,<br>
Jacob<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
HTTPS-Everywhere mailing list<br>
<a href="mailto:HTTPS-Everywhere@lists.eff.org">HTTPS-Everywhere@lists.eff.org</a><br>
<a href="https://lists.eff.org/mailman/listinfo/https-everywhere" rel="noreferrer" target="_blank">https://lists.eff.org/mailman/listinfo/https-everywhere</a></div></div></blockquote></div><br></div>