4 ms·
RFC-1945: Because the source of a link may be private information or may reveal an otherwise private information source, it is strongly recommended t
by iso1631 6y ago
RFC-1945: Because the source of a link may be private information or may reveal an otherwise private information source, it is strongly recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From information.
So not sending referrer has always been fine, and I suspect that firefox will have an option to enable the sending somewhere in it.
- pjmlp 6y agoNormal people are going to switch browser instead of trying to find the said option, because Firefox is "broken".
- wccrawford 6y agoI would say that most "normal people" don't even know the browser sends a referrer header, and it doesn't actually do anything for them. This is useful for site owners, and they have little control over what browser their users use. And as someone else already pointed out, the other big browser (Chrome) has already done this.
- fogihujy 6y agoWhy would this break anything? Which sites would break just because the referrer policy default setting changed? And why wouldn't sites have fixed that before, since Chrome pushed the same change last year?
- RHSeeger 6y agoSwitch to what, exactly? Chrome already does this, according to another poster.
- Mordisquitos 6y agoNormal websites are going to be unaffected in terms of user-facing functionality, regardless of whether they use the data gathered from HTTP Referer internally. On the other hand, badly designed websites that do depend on the HTTP Referer to provide functional user experience are going to lose their users in favour of normal websites, because they are "broken"—and always have been.