wiki: revisist smart referer recommendation
See original GitHub issuethe wiki mentions smart referer as a potential alternative to 1601
in case of breakage, and it also includes a couple tweaks (whitelist and strict mode).
however one of the default settings of SR is rewrite mode, quoting the readme of the project:
Rewrite Mode: Can be used to change what is sent to the server instead of the original referer header. The default (Send the URL you’re going to as referer) is known to cause the least issues on most sites and is therefore recommended.
this means that out of the box SR is spoofing referers which is not a good idea for security, and in fact it’s enforced false using 6002
.
the wiki should recommend changing rewrite mode to “Send nothing”.
Issue Analytics
- State:
- Created a year ago
- Comments:18 (6 by maintainers)
Top Results From Across the Web
HTTP referer - Wikipedia
In HTTP, "Referer" (a misspelling of Referrer) is an optional HTTP header field that identifies the address of the web page from which...
Read more >Wikipedia talk:Portal/Guidelines/Archive 8 - Wikipedia
Wikipedia talk:Portal/Guidelines/Archive 8. Project page Talk ... Concerning section: Recommended. 1. The second item from "Recommended" describes practice ...
Read more >Tesla Autopilot - Wikipedia
Tesla Autopilot is a suite of advanced driver-assistance system (ADAS) features offered by Tesla that amounts to SAE International Level 2 vehicle ...
Read more >Wikipedia talk:Reference desk/Archive 117
Wikipedia talk:Reference desk/Archive 117. Project page Talk. Language; Watch · Edit · Add topic. Active discussions. < Wikipedia talk:Reference desk ...
Read more >European Green Deal - Wikipedia
The plan is to review each existing law on its climate merits, and also introduce new legislation on the circular economy, building renovation,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here’s hoping uBO adds this - https://github.com/uBlockOrigin/uBlock-issues/issues/1663#issuecomment-1192832027 - then users can block by default but allow per eTLD+1. No Spoofing or affecting of CSRF. This is honestly the only way to do it IMO - simple on/off - I personally don’t think we need any of the complexity of origin vs destination
And it would be one less extension for those who use Smart Referrer. Most users wouldn’t want to disable all cross-site referers as per our default, it breaks too many platforms and properties. It’s fine for me, but I’m also happy to use uBO to break most 3rd party anyway.
The referrer pref 1601 is probably the biggest pref users have an issue with. If uBO added a block/enable per-site scope for this, then we could make that pref inactive, and just add a referer note to the uBO setup instructions
All I want is
What I don’t want