Rated 3.5 out of 5
3.5 Stars out of 5
- by Tulirebane, 3 years agoRated 2 out of 5This extension has three modes - block http, redirect to https or ignore. Since block http is the default, you either have to explicitly type https in front of every URL you visit or just get a blank page, because http is blocked.
It would make much more sense if it at least waited for/tried a https redirect before blocking, and displaying some kind of error message when blocked.
Developer responseposted 3 years agoThanks for the feedback. I’m afraid trying HTTP and checking for a redirect would defeat the point of this extension, as that HTTP request would be interceptable like any other.
If displaying an error page on blocked requests is possible without breaking requests for page resources, it’s next to be implemented; otherwise, the popup will at least open automatically.
Update 2018-06-06: Safeguard 0.5.1 displays an error page on the most common kind of blocked request.
- by co222, 5 years agoRated 5 out of 5very good.will beter if options when i select
allow,redirect or block to don't see them in popup and store rule on own file not in about:config
Developer responseposted 5 months agoAs of 0.6.1, released today, there’s an option to clear the history in the popup and a limited UI for managing rules (which, since moving to WebExtensions, are no longer stored in about:config). 🎉