Rated 4 out of 5 stars

by Elieux on April 24, 2012 · permalink

As with any whitelist, it took a while to set up RequestPolicy to my needs, but now my browsing is faster (no third-party ads, social plugins), more private (no social plugins again) and more secure (prevents potential XSS and CSRF attacks).

In future versions, I'd like to see improved handling of redirects (when a redirect to a payment gateway is blocked and then I allow it using the button in the yellow bar, it says "invalid request") and an option to mix "base domain" and "full domain" matching (e.g. allow destination googleapis.net, allow destination maps.google.com, but not *.google.com).