[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #11602 [Quality Assurance and Testing]: Make sure HTTPS-Everywhere ships with rules
#11602: Make sure HTTPS-Everywhere ships with rules
-----------------------------------------------+-------------------
Reporter: gk | Owner: boklm
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Quality Assurance and Testing | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-----------------------------------------------+-------------------
Comment (by gk):
Replying to [comment:4 boklm]:
> We currently have a test that check that https-everywhere is working by
visiting an http URL which has a rule
(http://www.mediawiki.org/wiki/MediaWiki) and checking that it results in
visiting the https URL (we also check that it doesn't do that when the
extension is disabled, in case the website starts redirecting
automatically one day). So I think this test would have detected this
problem.
Nice! Does the test catch corner-cases like a redirection to an HTTPS site
on mediawiki's side itself? I could imagine that they implement that one
day and then (depending on how the test works) passing might not say much
about a functioning HTTPS-E anymore...
> But I can also add a test that checks that rulesets.sqlite exists and is
not empty just to be sure.
>
> It would probably be a good idea too to check for any exception thrown
during TBB start-up, I will check if we can detect that (or if mozmill
already makes an error in that case).
Either way seems fine at least to detect the issue I encountered.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11602#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs