Compare what a saved referrer policy discloses
Admin ·
A catalog team wants to know which parts of a page URL accompany links to its own archive and a separate studio. Compare the same saved policy across both destinations.
Compare two catalog referrers
Choose Load example and Check referrer policy. The recorded field contains three tokens. The report selects strict-origin-when-cross-origin as the last recognized policy.
The catalog archive is same-origin, so the result says Full source URL and replaces the source path and query with placeholders. The separate HTTPS studio destination gets the source origin only.
Read the downgrade result
The third destination uses ordinary HTTP while the source is HTTPS. For the recorded policy, its predicted result is Omitted.
Compare the table’s Disclosure and Redacted Referer columns. Full source URL refers to the stripped URL the browser can send. The redacted report withholds private URL parts and shows only the source origin or placeholders. The standard substitutes the origin when the stripped URL exceeds 4,096 characters after serialization.
Check a saved policy value
Paste a header or an individual policy value to use the same destination list for a second comparison. When none of the recorded tokens are recognized, the report labels the strict-origin-when-cross-origin default assumption.
Copy or download the JSON report. Use it to document the recorded response policy and the hypothetical outcomes for the supplied destinations.
W3C Referrer Policy, policy parsing and referrer algorithmsWHATWG Fetch Standard
Common questions
Is the browser header spelled Referrer?
The policy field is Referrer-Policy. The spelling of the request field is Referer.
Does a fragment appear in the outgoing referrer?
The referrer algorithm strips fragments before considering the policy. The report also withholds paths and query values.