[HTTPS-Everywhere] Automatic testing of rules to discover rules that broke (e.g. by site redesign)

[Colonel Graff]

Hey Ondrej,

Peter and Scott have both been made aware of this, but these are the
first steps towards what you suggested. Already with them I've found a
few broken websites that I've fixed. Don't run them on your machine
though. They're highly imperfect. Feel free to add/improve them
though.
https://gitorious.org/https-everywhere-fork/https-everywhere-fork/blobs/graff/single_rule_response.py
https://gitorious.org/https-everywhere-fork/https-everywhere-fork/blobs/graff/trivial-response.py

For now these will just test the destination of the redirects that
don't have backreferences. No breadth first search yet. That wouldn't
be trivial. I might go ahead and write that later, but not right now.
As a non-CS person (I'm far more of a hobbyist) I haven't had the joy
of dealing with databases yet. If you'd like to add that to this or
send me a good tutorial for the future, I'd appreciate it.

On Tue, May 1, 2012 at 10:03 AM, Colonel Graff
<graffatcolmingov at gmail.com> wrote:
> On Sun, Apr 29, 2012 at 12:15 AM, Peter Eckersley <pde at eff.org> wrote:
>>
>> On Sat, Apr 28, 2012 at 06:50:01PM +0200, Ondrej Mikle wrote:
>> > Hi,
>> >
>> > seeing how many times "broken rule" topics appear in
>> > https-everywhere-rules,
>> > have you considered some automatic tests? (Re-reading the text of this
>> > mail
>> > again, I might be attempting to solve a problem you may not really
>> > have.)
>>
>> We would /love/ to have someone implement a proper test suite of this
>> sort!
>> We even offered it as a Google Summer of Code project this year, though we
>> didn't get any takers :(
>>
>> --
>> Peter Eckersley                            pde at eff.org
>> Technology Projects Director      Tel  +1 415 436 9333 x131
>> Electronic Frontier Foundation    Fax  +1 415 436 9993
>>
>> _______________________________________________
>> HTTPS-everywhere mailing list
>> HTTPS-everywhere at mail1.eff.org
>> https://mail1.eff.org/mailman/listinfo/https-everywhere
>
>
> I'm not entirely certain of the best way to do this, but if anyone's looking
> at doing it in Python (since we already use python for rule validation)
> check out Kenneth Reitz's excellent requests library. It handles https (if I
> remember correctly) and makes URL handling a lot easier.