-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP referer #13
Comments
I don't think you really want to block all HTTP headers... you won't see many websites if you do that! :-) I think you are just asking to block HTTP referers (aka HTTP referrers). I think it's a reasonable request. Note that Privacy-Settings currently allows toggling the setting for secure cross-site referers, but not for regular referers. Since blocking referers can (currently) break a few sites, there are a number of browser extensions that block referers and handle exceptions quite well. On the other hand, if more people blocked _all referers_, fewer web developers would create sites that require that easily-spoofed parameter. Since it is trivial to spoof an HTTP referer, it's not a good development practice to require any specific referer. |
Oh yes I am sorry I mean HTTP referrers! Yes it does rarely break some sites but I browse for like a half a year on all my devices without them and I remember a single broken page. I mean I think it was that. Since most people aren't aware that something like that even exists I doublt that it makes a difference on devs. |
Can you change the title of this issue? Thanks! I agree, deciding to not transmit HTTP referers usually has no negative effects (I would estimate more than 99% of the time). Fewer and fewer sites use them as a "protection" mechanism, since they are so ineffective for that use. That said, when a website is not working as expected, it creates another test-case to determine what went wrong. |
Done. Btw: There are the possible values 0,1 or 2 for referers. I dont know what 1 means. That might be an option as well. |
Refcontrol https://addons.mozilla.org/en-US/firefox/addon/refcontrol/ is the best option for this. set the default policy to block referrer and just allow/spoof for sites where its needed |
however there could be more private defaults set in firefox
|
personally i think ill use:
and just keep using refcontrol to block all and allow on a per site basis |
you can test your settings here http://www.whatismyreferer.com/ (click the url at the bottom of the page) |
Thanks for clarification! I chose everywhere the safest option. Don't care if it breaks pages or not. |
The problem is that you don't necessarily notice when a page 'breaks'. I haven't had any issues with |
I can't think of anything relevant for security in regards to the
tl;dr: use |
I like the idea of adding integer prefs, although, as you mention, it will be a bit more confusing. Whatever you do with referrers, remember that many systems use extensions that modify referrers on a per-site basis. For those systems, make sure you don't interfere with those extensions. |
I think the idea to control with Privacy-Settings more complex options is really great. So maybe you can expand the Addon with an Advanced Settings section and a FAQ on GitHub with explanations like from @berrythesoftwarecodeprogrammar and some warnings about breaking sites. I created a little mockup, how it could be implemented: |
I am thinking it might be more flexible if we have advanced settings listed in a browser tab. Having them on the panel might be confusing to some users. We are going to have a link to this page in the panel though. |
browser tab like done in Configuration Mania im guessing. if you want to keep a panel maybe have the quick settings + things people are likely to toggle/mess with regularly on the panel and have a link to the full settings page |
I think your addon should stop Firefox from sending HTTP headers (referer).
network.http.sendRefererHeader;0
Regards,
amilopowers
The text was updated successfully, but these errors were encountered: