Privacybadger: Plug-in compatibility issue

Created on 17 Aug 2015  路  6Comments  路  Source: EFForg/privacybadger

Referer Control 0.59

Warning:
This extension failed to modify the request header "Referer" of a network request because the modification conflicted with another extension (Privacy Badger).

Chrome wontfix

All 6 comments

This is because we strip the referer header from requests to domains that are cookie blocked.

@cooperq can't you add a option to disable this feature? Even if it is hidden/available only from about:config. Would it solve this conflict? I prefer use uMatrix extension to spoof HTTP referer because I can enable it for all websites.

By the way, once there is a conflict, will it prevent uMatrix spoof the referer even in the websites privacy badger is not doing anything?

@cooperq is there any chance of my request above be ever implemented? I'm looking for a solution for this issue. Another alternative may be an option to Privacy Badger do referer spoofing for all websites.

@semente I might consider an option to always spoof the referer header. What does umatrix replace the referer header with? Or does it just strip it? Please open a new issue for this feature request.

@cooperq awesome!

If this setting is checked, uMatrix will spoof the HTTP referrer information if the domain name of the HTTP referrer is third-party to the domain name of net request.

I think it is the best setup. Spoofing all requests may cause some issues (at least I already had authentication issues with some websites). Other option is send the URL you are going to visit as the HTTP referrer, but I found uMatrix solution better.

edit: I will open a new issue, thanks!

Related to #1134.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

smarkwell picture smarkwell  路  5Comments

tophtophtoph64 picture tophtophtoph64  路  4Comments

BlackRabbit22 picture BlackRabbit22  路  5Comments

intchloe picture intchloe  路  6Comments

mrphs picture mrphs  路  5Comments