50 recensioni per questo componente aggiuntivo
  • It's not 100% perfect, e.g. no Chrome version, a few bugs here and there, but all in all this seems fantastic. Nothing else seems to encapsulate this functionality (except Tor Browser), which is really a shame. The referer header is a significant source of information leakage which has been around since the web was invented. I'm surprised that this extension is perhaps the only way to defend against such leakage with ease. It certainly brings a greater peace of mind with respect to people being able to track your movements.

  • ขอบคุณ

  • I like your User Agent addon.
    Having the ability to set custom referrers for different websites would be nice.

  • fine :)
    smart :)
    simple :)

    Also for Chrome, Opera? :)

  • When i have enable the addon, i can't watch videos on Facebook...by disabling the addon everything is ok. The problem is only on FB...please fix that issue.
    Windows 7 64bit Firefox 61.0 beta 13

  • Good

  • Indispensable addon! A must have!

    Requests:
    Can it be possible to add exceptions from the toolbar icon?

  • Please write a release note.

  • It gives a piece of mind in terms of online privacy and security. I have not encountered any problem with it so far.

  • Great extension.
    If this extension add the Import/Export rules function,this extension will be better.

  • Awesome add-on!

  • I installed this as a replacement to RefControl, because of that WebExtension mess.

    I just installed it, so I'll have to test it longer to be sure, but so far I like the concept of only forging cross-doman requests: that seems like a smart way to avoid most of the trouble that could be caused by forging everything like I used to.

  • Awesome!

  • Great extension to protect our privacy, only one thing is missing for it to be a full WebExtension replacement for the legacy extension RefControl : please add an option for it to work on the same domain too !

  • the setting is strange and hard to understand use, for example how to set a site "*.google.com" reffer to "yahoo.com".
    please make that easy to use like RefControl.

  • Please keep this in mind for the webextension: ghacks.net/2017/08/30/firefox-webextensions-may-identify-you-on-the-internet/

  • Thanks for finally adding e10s / WebExtension support. I realized how much I missed this addon when I was relying on Firefox's built-in referrer controls. Some sites (like photos.google.com > youtube.com) simply do not work without a valid referrer. This addon lets my protect my privacy and still use all the sites I want. Keep up the great work! :)

  • Any novel privacy-enhancing add-on gets a thumbs up from me. Thanks!

  • I use this all the time. How is e10 compatibility coming along?

  • I like the fact the extension allows you to treat subdomains as different domains, and to configure how the referer should be set (same than URL or direct hit). The project is on GitHub: https://github.com/meh/smart-referer

  • I was using RefControl before but this one is better (more simple and just looks better). Plus this one works on Firefox Mobile unlike RefControl.

  • Not sure why everything online wants to spy on you nowadays...

  • Can't live without it!
    Thanks developer.

  • FlickR recently started preventing me logging in. Disabling Smart Referer resolved the issue. It's a shame, as it's been a reassuring add-on, but now unusable for me.

  • Since Firefox 28 there are three new items in about:config:

    network.http.referer.XOriginPolicy: 0=always send, 1=send if base domains match, 2=send if hosts match
    network.http.referer.spoofSource: false=real referer, true=spoof referer (use target URI as referer)
    network.http.referer.trimmingPolicy: 0=send full URI, 1=scheme+host+port+path, 2=scheme+host+port

    Referrer processing is done in this order. Thus, setting XOriginPolicy to 2 makes spoofSource and trimmingPolicy useless if going from a.example.com to b.example.com, since no referrer would be send anyway due to the XOriginPolicy.

    If using the three new I'd suggest to set the old network.http.sendRefererHeader to 2 (default, always send referrer).

    See https://bugzilla.mozilla.org/show_bug.cgi?id=822869