Add-ons
Reviews for RequestPolicy
211 reviews for this add-on
Rated 5 out of 5 stars
A very good add-on that puts an end to requests going on behind my back. It needs a certain period tough in which one has to manually add trusted sites to the whitelist when browsing them for the first time. But once this is done, it works smoothly in the background and adds very good extra protection. I recommend this in combination with NoScript, Adblock Plus, BetterPrivacy and CookieSafe.
P.S.
I also experienced a speed boost in browsing, because unnecessary requests are simply blocked, thus websites are displayed earlier.
Rated 4 out of 5 stars
It is a very useful addon, however, generates a lot of noise when connected to the web sites when I do a search on google, should have more options for the web forwarding as well as the ability to manually add the domain as reliable as malicious.
This review is for a previous version of the add-on (0.5.13).Hi, I don't fully understand the feature you're asking for. Please email me or find me on irc so we can discuss it. Thanks!
Rated 5 out of 5 stars
Please tweak the addon so that the page will only do one reload after all the chosen options are toggled. NoScript pioneered this behaviour, and it's useful for saving bandwidth.
This review is for a previous version of the add-on (0.5.13).This is definitely a feature that will be added (ticket is here: https://www.requestpolicy.com/dev/ticket/2). There's quite a number of features that need to be added first, but this is a very popular request.
Rated 5 out of 5 stars
I'd like to be able to approve *.imageshack.us and *.tinypic.com either outright or in association with certains sites or forums. Since imageshack adds new hosts often it's troubling to add each one at a time. There are other sites like this with similar CDN*.somesite.tld that are as irksome to whitelist. ... not merely to load content but 'allow' redirection
despite these this is a truly excellent security extension that falls into "must have" category for EVERY firefox profile.. even those light on extensions
whitelist from *.there.tld
whitelist from cdn*.why.tld
blacklist such that I never am prompted again, nor shown in blocked menu
Rated 4 out of 5 stars
Very good, but an important thing is missing - wildcard or regexp support, so you can use the full address mode for unfamiliar sites or untrusted subdomains, but don't have to add many permissions for trusted sites and subdomains. Blocking an untrusted subdomain might require a blacklist though.
This review is for a previous version of the add-on (0.5.13).Rated 5 out of 5 stars
This add-on has my firefox running 1000X better since I replaced NoScript with Requestpolicy. I even tweeted about it. Keep it light and you've got me as a loyal adopter!
This review is for a previous version of the add-on (0.5.13).Thanks, I'm glad you like RequestPolicy. I personally suggest using both RequestPolicy and NoScript. See the following for more info on why: http://www.requestpolicy.com/faq#faq-noscript
Rated 4 out of 5 stars
The extension is great, but as I think there is no opportunity to allow all reqs by default while blocking only unwanted requests? Additional site blacklists could be exchanged and imported from user-community.
Perhaps I am doing it wrong, but trying to allow different blocked reqways to find which one is responsible for missing images(f.e.) is kind of exhausting.
Rated 5 out of 5 stars
RequestPolicy is still my choice, thanks for the 0.5.13 feature of disabling auto-reload!
This review is for a previous version of the add-on (0.5.13).Rated 2 out of 5 stars
I love the concept. Unfortunately, it does not seem to work with StumbleUpon (or StumbleUpon does not work with it) despite stumbleupon.com being whitelisted for both source and destination. Yes, I could turn it off temporarily while "stumbling," but that is when I most desire protection as I never know where the Stumble button will take me. Anyhow, what happens when you press the "Stumble" button is that StumbleUpon picks a topic, displays the topic and "discoverer" of the page in the StumbleUpon bar, but the page itself is never displayed.
This review is for a previous version of the add-on (0.5.13).This works for me when I whitelist stumbleupon.com as an origin (that is, selecting "allow requests from stumbleupon.com" from the menu). If you're still having problems with this, please let me know.
Rated 5 out of 5 stars
Excellent add-on, a must have!
Please note that on hiding the status bar the icon on the Navigation toolbar gets disabled (shows nothing, does nothing). Kindly address this issue!
Rated 5 out of 5 stars
Since the author has corrected the file:// policy in the latest version 0.5.13, I now give back five-star for the hard work and rapid respond by the author of this great addon. Thanks very much, truly!
This review is for a previous version of the add-on (0.5.13).Rated 5 out of 5 stars
Please ignore previous comment. It turns out that 3.6 is highly unstable on OpenSolaris at the moment and it's not RequestPolicy's fault.
This review is for a previous version of the add-on (0.5.12).Thanks for following up to say it doesn't appear to be a RequestPolicy bug. I had noticed your comment and opened a ticket for this, which I have now closed (https://www.requestpolicy.com/dev/ticket/73). You did make me realize that I have never tested on OpenSolaris and should be running a VM for it.
Rated 5 out of 5 stars
Works very well. Frankly I haven't seen a must-have security extension like this since I installed BetterPrivacy and that was a long time ago.
This review is for a previous version of the add-on (0.5.12).Rated 1 out of 5 stars
I would love to give it five-star. HOWEVER, since the last update, RP just block whatever request from a local HTML file, that is, when another extension bring up its local document window, RP blocks it; when I open a ScrapBook item, RP blocks it. It is terribly painful to add each file to the white list -- that's right, you CAN'T even set a path with "file://" to bypass local files, it must be exact file path for each one!
What a damn good idea to put a hand on my "local security"! Thanks a lot but not any more.
I apologize for the very slow response to this bug. In case it helps, installing the older version 0.5.8 would likely make this usable again for you until I can fix this issue. However, no matter how busy life has been, it doesn't excuse not fixing a bug reported months ago. I will fix this bug this coming weekend, period. (The new version might not appear on addons.mozilla.org for a few weeks, though.)
Rated 3 out of 5 stars
For some reason the 'allow requests from (e.g.) Amazon.com' option has disapeared and I have to click 'temporarily allow requests from....' instead, which is very annoying. I think this happened after an update, it used to be there.
This review is for a previous version of the add-on (0.5.12).Hi, I'm sorry this change was frustrating. Version 0.5.8 did not treat private browsing mode differently. Since the update to 0.5.12, when the browser is in private browsing mode, the RequestPolicy menu does not give the option of permanent whitelisting. This is a privacy feature, but I didn't realize how many people use private browsing by default and this has hurt usability for these users. I have a ticket open for this issue and it will be addressed in the next release: https://www.requestpolicy.com/dev/ticket/58
Rated 5 out of 5 stars
I'm so glad I discovered this plugin. Been running Adblock/NoScript for a good long while but still found them lacking because neither handle cross-site requests, which I was keen to get control of as so many sites out there access all manner of unwanted off-site rubbish during browsing, totally ruining any chance of privacy and so on. Thankfully I discovered RequestPolicy as this seems to do exactly as I needed, and I'm happy to say it's worked fine so far.
I guess it takes some degree of skill to operate, similar to running the NoScript extension, so may not appeal to some people out there, but for anyone like me looking for strong control over how Firefox runs around the web, this could be just the thing.
No serious criticisms here, though the menu Red/Green text was a little difficult to read against the Nasa Night Launch (dark) window theme I was running, so I was thinking it could benefit from an option to set colours in config to cure that. The red on black in particular gets a little hard to see. Other than that it's all good!
Rated 5 out of 5 stars
I'm so glad I discovered this plugin. Been running Adblock/NoScript for a good long while but still found them lacking because neither handle cross-site requests, which I was keen to get control of as so many sites out there access all manner of unwanted off-site rubbish during browsing, totally ruining any chance of privacy and so on. Thankfully I discovered RequestPolicy as this seems to do exactly as I needed, and I'm happy to say it's worked fine so far.
I guess it takes some degree of skill to operate, similar to running the NoScript extension, so may not appeal to some people out there, but for anyone like me looking for strong control over how Firefox runs around the web, this could be just the thing.
No serious criticisms here, though the menu Red/Green text was a little difficult to read against the Nasa Night Launch (dark) window theme I was running, so I was thinking it could benefit from an option to set colours in config to cure that. The red on black in particular gets a little hard to see. Other than that it's all good!
Rated 5 out of 5 stars
Sorted out the images in brief courtesy of the work around by Phlox by now it tells me I have another conflict with Brief, takes me to the Request Policy web page confirming a conflict exists and suggesting I look at the conflict tickets but there is no reference to this conflict. Also can't see what the conflict is, baffling!
This review is for a previous version of the add-on (0.5.12).Rated 5 out of 5 stars
I like it very much. Its simple but so helpfully. Everybody should have it when surfing with Firefox.
This review is for a previous version of the add-on (0.5.12).Rated 3 out of 5 stars
Good Idea but Too Much .... that is if you have assembled the programs you need to make a reliable policy choice - NoScript,Ghosteray, CounterPixel, etc.
They not only give you a choice of detailed information needed to answer RequestPolicy, but they are already taking steps to either block a site or draw its fangs.
If I approve something in NoScript, which takes action, doing what I need to do to lower the Red Flag is a bit redundant.
The cure would be for the author to work with NoScript - a fantastic program at blocking intruders known or unknown to you, Ghosteray, for some reason Not As Popular because it ID's infotheft organizations ala DoubleClick, and, without EVER SAYING SO (I've suggested this to author) BLOCKING every one it can name, Counterpixel, which, as far as I've determined, neither blocks nor shows the offending screen pixels, the (untested here) PluginChecker, which should block or at least ID plug-ins installed by persons other than those at your keyboard, etc.
(oh, I'm leaving NettiCat's work out and a dozen others)
AND producing a single policy program - what is allowed always, what is NEVER allowed without a specific unlock from the User, what policies are site- or even page-related, permanently or just for a d/l.
THAT'S what we desperately need, a single report on EVERYTHING a site is throwing at us, so we can give appropriate answers - and what we do not have ... yet.
Good Idea which does too much of what others still do better E for Effort.
To create your own collections, you must have a Mozilla Add-ons account.
