We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

تلاش سپورٹ

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

مزید سیکھیں

اس تھریڈ کو آرکائیوکیا گیا تھا۔ اگر آپ کو مدد کی ضرورت ہو تو براہ مہربانی نیا سوال پوچھیں۔

Firefox private browsing trims request referrer headers.

  • 1 جواب دیں
  • 1 میں یہ مسئلہ ہے
  • 7 دیکھیں
  • آخری جواب بذریعہ philipp

matthew.was
matthew.was
more options

A site I develop for checks authenticity by checking a passed value confirming it it valid for a given referring url. The request has a referrer header which in regular windowed firefox is the full url of the requesting site. In private browsing mode the referrer header is only the host part of the url and does not contain the full path. It is the path that is commonly required to verify the site. Is this expected behaviour or a bug?

This has been confirmed both on macOS and Windows 10 using Firefox Quantum 61.0.

A site I develop for checks authenticity by checking a passed value confirming it it valid for a given referring url. The request has a referrer header which in regular windowed firefox is the full url of the requesting site. In private browsing mode the referrer header is only the host part of the url and does not contain the full path. It is the path that is commonly required to verify the site. Is this expected behaviour or a bug? This has been confirmed both on macOS and Windows 10 using Firefox Quantum 61.0.

تمام جوابات (1)

philipp
philipp
  • Moderator
more options

hi, yes that appears to be the intended behaviour accoring to https://blog.mozilla.org/security/2018/01/31/preventing-data-leaks-by-stripping-path-information-in-http-referrers/