Referer header missing or truncated: Referrer-Policy strips it
Your analytics, hotlink protection or CSRF check sees an empty or origin-only Referer because browsers apply a strict default policy.
Referer header missingReferrer-Policy no-referrerHTTP_REFERER emptyReferer is empty cross-origindocument.referrer is empty Meaning
Modern browsers default to strict-origin-when-cross-origin, and Referrer-Policy: no-referrer or HTTPS→HTTP navigation removes it entirely. Set a policy that fits your use (same-origin for internal checks), don't rely on Referer for security, and use Origin or tokens instead.
Common causes
Referrer-Policy: no-referrerheader or meta tag- HTTPS to HTTP navigation drops Referer
- Default strict-origin-when-cross-origin trimming the path
rel="noreferrer"on links- Privacy extensions
⚡ Quick fix
- Set
Referrer-Policy: strict-origin-when-cross-origin(or the one you need) - Use tokens/Origin, not Referer, for checks
- Avoid HTTP links from HTTPS pages
Detailed fix by platform
HTTP
Referrer-Policy: strict-origin-when-cross-origin
How to diagnose
- Policy — Which value?
- Navigation — HTTPS to HTTP?
- Check — Relies on Referer?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026