News for hackers. Stuff that matters.

A comment on Switching to Firefox, Concerned with UBlock Origin Changes. Parent comment

Re:Switching to Firefox, Concerned with UBlock Origin Changes by jameslk on Tuesday February 05, 2019 @12:18PM (#19087308)
I think the reason Google does this is to prevent the site you're landing on from knowing what you searched for through the HTTP Referer header.
[ Parent | on HN ]
Re:Switching to Firefox, Concerned with UBlock Origin Changes by jakeogh on Tuesday February 05, 2019 @09:28PM (#19092178)
That header is the user-agent's decision, I consider it an anti-user feature. Google (like most search engines) wants to know what you clicked on.
[ Parent | on HN ]
Re:Switching to Firefox, Concerned with UBlock Origin Changes by zenexer on Wednesday February 06, 2019 @01:16PM (#19097919)
That's correct. Google uses Referrer-Policy [1] to prevent the full referrer from being sent to the destination website. The transition page is purely for tracking. The ping attribute [2] is meant to replace that transition page eventually, but it needs to be ubiquitous and equivalent in terms of features before Google switches to that method.

[1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re...

[2]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#...

[ Parent | on HN ]
Re:Switching to Firefox, Concerned with UBlock Origin Changes by Nicksil on Tuesday February 05, 2019 @12:51PM (#19087624)
I vaguely recall the `rel` attribute value "noreferrer" on the anchor element producing this behavior; is that not the case (any more)?
[ Parent | on HN ]
Re:Switching to Firefox, Concerned with UBlock Origin Changes by zenexer on Wednesday February 06, 2019 @01:17PM (#19097933)
That's graduated into Referrer Policy, more or less, but it should still work.
[ Parent | on HN ]