←back to thread

944 points 6a74 | 1 comments | | HN request time: 0s | source
Show context
hentrep ◴[] No.41802660[source]
I noticed the URL was updated for this post. Previously it linked to asahilinux.org which showed an anti-HN manifesto from the HN referral. Curious as I haven’t seen this before. Seems it has been covered by previous commenters: https://news.ycombinator.com/item?id=36227103
replies(5): >>41802728 #>>41802899 #>>41803142 #>>41803235 #>>41803470 #
ginko ◴[] No.41802728[source]
How can the site even detect where a user is coming from? Browsers leaking this information seems like a huge privacy issue to me.
replies(1): >>41802741 #
robin_reala ◴[] No.41802741[source]
Referer (misspelled in the spec) has been a part of HTTP from day 1.
replies(1): >>41802788 #
ginko ◴[] No.41802788[source]
Feels crazy this isn’t disabled by default
replies(5): >>41802839 #>>41802862 #>>41802919 #>>41802996 #>>41803993 #
Smar ◴[] No.41802862[source]
There is little hope to get it disabled when an ad company is running running the most popular ad platf... Erm, the world wide web browser.
replies(1): >>41802931 #
1. jsheard ◴[] No.41802931[source]
The Referrer-Policy header lets a server tell the browser how much referrer information to pass on when following links, all the way down to nothing at all if desired. Chrome does respect that, and they also followed other browsers in changing the default to "strict-origin-when-cross-origin" a few years ago which truncates the referrer path when leaving to a different domain, so they only see the domain the visitor came from rather than the specific page like they used to. Can't really fault Google in this case.

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