The origin-when-cross-origin Referrer-policy HTTP header (and meta tag) limits referrer information whether or not the request downgrades the URL scheme (https-to-http vs https-to-https; see examples at https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy#Directives). The existing language seems to imply that a third-party website that upgrades to HTTPS can expect to receive resource URLs in their referrers after they update to HTTPS, which is not the case.
Here I propose new language to clarify what third parties should expect from the recommended referrer policy.
The origin-when-cross-origin Referrer-policy HTTP header (and meta tag) limits referrer information whether or not the request downgrades the URL scheme (https-to-http vs https-to-https; see examples at https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy#Directives). The existing language seems to imply that a third-party website that upgrades to HTTPS can expect to receive resource URLs in their referrers after they update to HTTPS, which is not the case.
Here I propose new language to clarify what third parties should expect from the recommended referrer policy.