Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

document.referrer doesn't return page path

  • 5 个回答
  • 2 人有此问题
  • 416 次查看
  • 最后回复者为 ArmandChoy

more options

I have a page that is loaded through apps.facebook.com

There are two paths that this page can be accessed from: apps.facebook.com/ProductionPage apps.facebook.com/DevelopmentPage (Not the actual urls, just used as an example)

I was using document.referrer to determine if the page was loaded through the Development path and if so load some debuging code. Now firefox was updated so document.referrer only returns the domain without the path. Is there any way or workarounds to get that path from the document.referrer?

Thanks, Armand Choy

I have a page that is loaded through apps.facebook.com There are two paths that this page can be accessed from: apps.facebook.com/ProductionPage apps.facebook.com/DevelopmentPage (Not the actual urls, just used as an example) I was using document.referrer to determine if the page was loaded through the Development path and if so load some debuging code. Now firefox was updated so document.referrer only returns the domain without the path. Is there any way or workarounds to get that path from the document.referrer? Thanks, Armand Choy

被采纳的解决方案

The most obvious workaround seems to be to add a parameter to the URL you use to embed into the page, assuming FB allows that.

定位到答案原位置 👍 1

所有回复 (5)

more options

hi, maybe the following blog post can be of help?: https://blog.mozilla.org/security/2015/01/21/meta-referrer

more options

Wow, I didn't know about this change. FB is using:

<meta name="referrer" content="origin-when-crossorigin" id="meta_referrer" />

So yes, apps hosted on other hosts do not get the full URL under that policy:

http://www.w3.org/TR/referrer-policy/#referrer-policy-state-origin-when-cross-origin

more options

选择的解决方案

The most obvious workaround seems to be to add a parameter to the URL you use to embed into the page, assuming FB allows that.

more options
more options

jscher2000 said

The most obvious workaround seems to be to add a parameter to the URL you use to embed into the page, assuming FB allows that.

While this doesn't solve the "problem" with document.referrer, I found out that facebook allows you to pass parameters to your page when you load apps.facebook.com.

Thanks for the replies!