If Mozilla genuinely prioritized its users' interest it would block ads and tracking networks, which are the major way people's private information is leaked and also a primary vector for hacking. And yet for some mysterious reason Firefox hasn't broken ranks with Google by incorporating ad blocking. Even though its an obvious major feature and Firefox is losing marketshare every year. We know why Google won't priori…
Firefox 59 to strip path information from referrer values for 3rd parties
71–80 of 236 posts
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#72Earlier quoted context omitted.
As someone that doesn't dig into this data for a living, why would you not want this on non-private sessions (first question I had when reading this)? I'm curious why Mozilla wouldn't want to protect this data leaking in even a normal session.
> why would you not want this on non-private sessions Information leaks. You click a link from your email to a news article. The URL for the news article has your email in it. Then you click an ad on the news article. The ad just got your email address. Worse still - instead of an email address, it's a token that auto signs you in to your account with the news site. Sites are pretty bad at sanitizing their outgoing r…
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#73As someone that digs in this data for a living, personally strongly believe this should be on by default for all browsing. The example they give is an insanely bad design for healthcare.gov and I would absolutely not want to find that type of data in my analytics telemetry. It is very useful to know where your traffic is coming from, but that’s usually viewed at a higher level than the querystring params being shown.…
As someone that doesn't dig into this data for a living, why would you not want this on non-private sessions (first question I had when reading this)? I'm curious why Mozilla wouldn't want to protect this data leaking in even a normal session.
However, if “you” is a company that is in some other business, but collects analytics for the purposes of optimizing it’s product and figuring out what actually works for their users, then you don’t event want to run the risk of ingesting something private. Especially with exposure to different jurisdictions.
Think of it as the difference between a double-opt-in email list where you are very sure people want to receive the communications and an unsolicited spam list. If the user volunteers this data and it has some relevant business purpose, that’s great. However, if the user doesn’t know I have this info and wouldn’t want me to have it, then acting on that data could create a lot of negative emotions that as a company I wouldn’t want.
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#74As someone that digs in this data for a living, personally strongly believe this should be on by default for all browsing. The example they give is an insanely bad design for healthcare.gov and I would absolutely not want to find that type of data in my analytics telemetry. It is very useful to know where your traffic is coming from, but that’s usually viewed at a higher level than the querystring params being shown.…
As someone that doesn't dig into this data for a living, why would you not want this on non-private sessions (first question I had when reading this)? I'm curious why Mozilla wouldn't want to protect this data leaking in even a normal session.
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#75In about:config, setting 'network.http.sendRefererHeader' to 0 (default is 2) will stop the referer header from being sent, and the document.referrer from being set. See http://kb.mozillazine.org/Network.http.sendRefererHeader for more information.
Description: "If a page hasn't set an explicit referrer policy, setting this flag will reduce the amount of information in the 'referer' header for cross-origin requests."
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#76Earlier quoted context omitted.
Also paywall skipping, to track what sites are bringing you traffic, to pass fields to forms to report problems, to present targeted traffic based on use, and of course, advertising.
The question was for reasons to __not__ remove them.
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#77Earlier quoted context omitted.
It might break websites that provide features based on the referrer (eg. a central authentication that redirects back to the original page)
I can't recall ever encountering a referer-based authorization scheme that included the path or querystring in its logic--although it seems likely some goofus has implemented it, somewhere.
We could, of course, build the same functionality into our implementation without relying having the path/query in the referer.
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#78Are there any reasons not to get rid of referers altogether?
Preventing CSRF attacks: https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(...
Anyone knows a good document on when/which browser actually sends referer header?
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#79Are there any reasons not to get rid of referers altogether?
If you have a giant traffic spike, it's nice to know where it came from. Eg. if you get linked on Hacker News, you can go to the thread and engage with potential customers.
Re: Firefox 59 to strip path information from referrer values for 3rd parties
#80Earlier quoted context omitted.
As a user I don't want you to know that information. I wish there was a way to click on links with the referer field removed entirely from the request(maybe via context menu)
You can sort of do that, context menu -> copy url -> open a new tab -> paste url