Referrer-Policy #50
Description
Please confirm that:
- You have read and understood the requirements for registration.
- You have checked the registry and found no current value that meets your needs.
- Your specification reference URL is stable; ideally, managed by a widely-recognised standards development organisation (e.g., published as an RFC). Otherwise, please give additional information below.
If so, please provide the details of your request below.
- Field name: Referrer-Policy
- Status: provisional
- Specification document(s): https://www.w3.org/TR/referrer-policy/#referrer-policy-header
- Comments: The header name does not share the HTTP Referer header’s misspelling.
Any additional information (this will not be included in the registry)?
This is a third-party request.
I have previously filed an issue with the specification's editor signalling the absence of this registration. There was no response to this issue.
I thought it was important to have it registered anyway. The header has been supported by most browsers for years. It is also commonly mentioned in security best practices (e.g. by OWASP's HTTP Security Response Headers Cheat Sheet).
I took the comment verbatim from the specification.