3 ms·
Totally agree. As almost no one uses anything like webmentions, this was the way to discover who was linking to your site. (And because the Google link tool did
by leephillips 6y ago
Totally agree. As almost no one uses anything like webmentions, this was the way to discover who was linking to your site. (And because the Google link tool didn’t seem to return much actual information.)
- nerdponx 6y agoBring it back! https://news.ycombinator.com/item?id=26401955 https://news.ycombinator.com/item?id=26401955
- myfonj 6y agoFrom a glance at MDN [1] and specs [3] it seems at least we can still opt-in our sites to suggest visitors user agent to pass full referrer address along outgoing links; there seems to be three ways to do so: # 1. Apache conf Header set Referrer-Policy "no-referrer-when-downgrade" <!-- 2. meta HTML head with same effect [2] --> <meta name="referrer" content="no-referrer-when-downgrade"> <!-- 3. HTML anchor attribute --> <a href="https://…" referrerpolicy="no-referrer-when-downgrade"> This will pass full path and query when navigating between HTTPS to foreign origin. I guess it will be lost in http: to https: redirects. `unsafe-url` value would do it even for HTTP. (Funny all three have different spelling, and that in effect they direct value of a single HTTP header with inherently erroneous spelling.) [1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re... [2] my guess using `<meta http-equiv="Referrer-Policy" content="no-referrer-when-downgrade">` should do the same, but is not explicitly mentioned anywhere. [3] https://w3c.github.io/webappsec-referrer-policy/ https://w3c.github.io/webappsec-referrer-policy/
- simias 6y agoNote that it only works if it's set on the source page, for obvious reasons. So if you set these headers on your page the browser will send the referrer when browsing away from your page, but not when your page is the target.