Ares mentioned he uses RefControl here. There is also a testing page to check whether the referrer is transmitted.
I installed it and wanted to test it via the preview feature but FF still transmits the referrer (I added forums.lanik.us to the list of RefControl and set it to "block").
Any ideas?
RefControl does not work here/on phpbb forums?
I've been using it for a little while now I think your problem is that it is not configured properly. I have it set so that it always sends the base url of the site and it works fine on the test link. It does cause problems now and then so keep that in mind when sites don't work.
It does not work for the first 3 sites. If I got to http://www.stardrifter.org/refcontrol/ and click on the test page at the bottom, no referrer is transmitted.
I set my up similar to yours and when I load the test page the referrer is blank (as it should be), I'm not sure what is causing your problems
That's weird. I tried it with an other FF profile. Same problem.
"Site" means "destination site" (=the one that receives the referer), not the site you are coming from.
Example link: http://www.google.com/
If you click on the link here, adding lanik.us <Block> will not block the referer, you have to add google.com <Block> to do that.
So if you don't want other sites to know that you are coming from lanik.us, you will have to set the default setting to <Block> or <Block> (3rd party) or <Forge>.
Example link: http://www.google.com/
If you click on the link here, adding lanik.us <Block> will not block the referer, you have to add google.com <Block> to do that.
So if you don't want other sites to know that you are coming from lanik.us, you will have to set the default setting to <Block> or <Block> (3rd party) or <Forge>.
D'oh! Thanks for clearing that up.
I know this thread is old but i've a good reason to suggest beefree!!!!!!!!!!!!!!!!!!!!!!!!!!!Ares2 wrote:"Site" means "destination site" (=the one that receives the referer), not the site you are coming from.
Yeah, beefree does the opposite of what refControl does!!!!!!!!!!
Actually, only in the first couple of versions it was doing the right opposite to refControl since beefree version 1.7, it will always remove the HTTP referer automatically when you're surfing from one server to another!!!!!!!!!!!!!!!!!!
I think that making one automatic system was a very nice idea!!!!!!!!!!!
So, every time that you're moving from server1.com to server2.com the HTTP-referer is removed without needing of lists to file!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
But, if you're moving from server1.com/index.php to server1.com/login.php then the referer is kept!!!!!!!!!! In this way, many websites won't stop to work!!!!!!!!!!!
bye!!!!!!!!!!!!!!!!!!
The bee is more honored than others, not because the bee labors, but because the bee labors for others.
While removing referrers is generally a good idea, it can cause problems for website buttons redirecting to the W3 validator, as the default button links to http://validator.w3.org/check?uri=referer. Would it be possible to "whitelist" the site in beefree?
Hi Michael!!!!!!!!!!!!!
There is no way to whitelist a website or even better a single page, using beefree i don't even know how to implement a whitelist feature
Although sending the referrer to the W3C validator is probably the only exception you could have
The only thing that pops up in my mind, is to disable beefree before clicking on that link you could enable the status-bar icon to quickly disable beefree at runtime, with a single click!!!!!!!!!!
bye!!!!!!!!!!!!!!
There is no way to whitelist a website or even better a single page, using beefree i don't even know how to implement a whitelist feature
Although sending the referrer to the W3C validator is probably the only exception you could have
The only thing that pops up in my mind, is to disable beefree before clicking on that link you could enable the status-bar icon to quickly disable beefree at runtime, with a single click!!!!!!!!!!
bye!!!!!!!!!!!!!!
The bee is more honored than others, not because the bee labors, but because the bee labors for others.
why using refcontrol or any other extensions when you can do it in about:config?
just set
network.http.sendRefererHeader to 0
and
network.http.sendSecureXSiteReferrer to false
just set
network.http.sendRefererHeader to 0
and
network.http.sendSecureXSiteReferrer to false
Refcontrol can do more than just not send the referrer (which breaks a lot of sites). It can fake the referrer which is as good as not sending it at all but with much less site breakage...
Well, these keysJoe wrote: any other extensions when you can do it in about:config
http://kb.mozillazine.org/Network.http. ... ererHeader
http://kb.mozillazine.org/Network.http. ... teReferrer
are ok to remove the REFERER header indiscriminately so, they're going to break a lot of websites beefree removes the referrer, only when it's necessary
It's also possible with beefree to fake the referrer!!!!!!!! i wrote the code for doing it, though i never tested if it works for real if it works, you could force an arbitrary referrer for one particular filter or also, for all filters
bye!!!!!!!!!!!!!!!!
The bee is more honored than others, not because the bee labors, but because the bee labors for others.
I've set up RefControl to forge the referrer across domains only as I've experienced some problems with secure sites otherwise. I'm content with my level of privacy as long as I can't be tracked across domains that easily.
Zombie Contributor