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!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Why won't Firefox obey <meta name="referrer" content="no-referrer"> meta tag sent in header?

  • 1 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 willsonkr

more options

I need to instruct browsers visiting my site to send a blank referrer back to the site when navigating internally to defeat some tricky bots that have been plaguing us by automatically spoofing the referrer as us. To foil their access I am forcing a captcha on all reported internal referrals.

Firefox is the only browser that insists on reporting the referrer, even when confronted with the meta tag not to.

I am aware of the method to cause it to hide the referrer in local settings, but this doesn't help the random visitor.

Does Firefox prefer another tag (I also tried "none", no luck)? Kind of stumped at it's refusal to cooperate with the standard header instruction. As far as I can tell all other browsers are cooperating.

I need to instruct browsers visiting my site to send a blank referrer back to the site when navigating internally to defeat some tricky bots that have been plaguing us by automatically spoofing the referrer as us. To foil their access I am forcing a captcha on all reported internal referrals. Firefox is the only browser that insists on reporting the referrer, even when confronted with the meta tag not to. I am aware of the method to cause it to hide the referrer in local settings, but this doesn't help the random visitor. Does Firefox prefer another tag (I also tried "none", no luck)? Kind of stumped at it's refusal to cooperate with the standard header instruction. As far as I can tell all other browsers are cooperating.

所有回覆 (1)

more options

Note: I did just realize the issue might have been a missing trailing slash, but changed the tag to: <meta name="referrer" content="no-referrer"/> and still no bueno.