Live data from Hacker News

Firefox 59 to strip path information from referrer values for 3rd parties

blog.mozilla.org

31–40 of 236 posts

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#31

Wouldn't this make it obvious that the user is browsing in private mode? While I get that might be preferable to leaking information, its also not an ideal solution either.

Not practically, no, since the approach is the same as setting the Referrer-Policy header to strict-origin-when-cross-origin. In most cases it can't be reliably deduced whether a visitor legitimately came from https://reddit.com/ (from the root origin) or some path on https://reddit.com/.

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#32
post #16
post #7

Earlier quoted context omitted.

They are useful to prevent the hotlinking of images/video from third party domains, which can incur in significant bandwidth costs for smaller websites.

That would continue to work fine with a default same origin allowance. A separate domain would require a referral policy.

Origin policy is a client thing. Referrer is accessible to the server. It's like using robots.txt vs. HTTP Auth to protect your content.

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#33
post #30

For those confused as to why half the comments have "misspelled" referrer, here's an interesting bit of history: The misspelling of referrer originated in the original proposal by computer scientist Phillip Hallam-Baker to incorporate the field into the HTTP specification. The misspelling was set in stone by the time of its incorporation into the Request for Comments standards document RFC 1945; document co-author Ro…

> Phillip Hallam-Baker

Funny how the misspelling of a double consonant comes from someone who has a misspelt given name with an extra double consonant!

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#34
As 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. In some cases, this may restrict you from knowing which article the person was reading on the given site before clicking through to yours, but if that’s so important, there are other ways to instrument source tracking.

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#35

> To help prevent third party data leakage while browsing privately , Firefox Private Browsing Mode will remove path information from referrers sent to third parties starting in Firefox 59. Emphasis mine. It only does it in private mode. I experimented with the referrer options mentioned in the article with mixed success. Not sending the referer header breaks some sites and often in a non-obvious way. EDIT: referrer…

Just curious, did it break any popular website?

I breaks a lot of things that do hotlink checks.

Maybe only allow a referrer from the same site policy?

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#37
post #33
post #30

For those confused as to why half the comments have "misspelled" referrer, here's an interesting bit of history: The misspelling of referrer originated in the original proposal by computer scientist Phillip Hallam-Baker to incorporate the field into the HTTP specification. The misspelling was set in stone by the time of its incorporation into the Request for Comments standards document RFC 1945; document co-author Ro…

> Phillip Hallam-Baker Funny how the misspelling of a double consonant comes from someone who has a misspelt given name with an extra double consonant!

In the U.S., apparently both "Phillip" and "Philip" are equally popular: https://www.ssa.gov/oact/babynames/

Edit: I'm glad you made this comment. I only know people with the name "Phillip" but I constantly find myself double-checking how their name is spelt before I refer to them (in text). I chalked it up to me being a bad friend but I guess it doesn't help that I might be seeing enough of the "Philip" variation to get confused.

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#38
post #25

Earlier quoted context omitted.

Just curious, did it break any popular website?

It will break forums and imageboards in my experience. Perhaps due to CAPTCHA.

Lots of sites use it to prevent other sites from stealing bandwidth

Re: Firefox 59 to strip path information from referrer values for 3rd parties

#39
post #33
post #30

For those confused as to why half the comments have "misspelled" referrer, here's an interesting bit of history: The misspelling of referrer originated in the original proposal by computer scientist Phillip Hallam-Baker to incorporate the field into the HTTP specification. The misspelling was set in stone by the time of its incorporation into the Request for Comments standards document RFC 1945; document co-author Ro…

> Phillip Hallam-Baker Funny how the misspelling of a double consonant comes from someone who has a misspelt given name with an extra double consonant!

I don't think you can ever describe a person's name as spelled correctly or incorrectly. It's spelled how they spell it. It's their name, not a dictionary's. Variations in spelling are perfectly natural and for names in particular are incredibly common
Post reply on HN