Re: [whatwg/fetch] Referrer policy: Should request's referrer policy be updated in the main fetch? (#266)

> I'm not sure what you mean with "existing" and "update the policy".

Sorry for not being clear.
"referer (existing)" means the HTTP referer header going to the network with the current specified behavior.
"referer (updating the policy)" means the HTTP referer header going to the network if we pass the combined referrer policy to the service worker. "Combined referrer policy" means the combined referrer policy from the request's referrer policy and the environment referrer policy.

> But the "referrer" is actually set at the beginning of Fetch to the result of applying the referrer policy. And then that "referrer" is passed on to the service worker. 

> So once the page policy is applied, the service worker never sees the original referrer, it only gets a trimmed down one (potentially even a "no-referrer" one). It won't be able to turn that back into a full referrer as far as I can tell.

I agree that the service worker only sees the referrer string applied the referrer policy. It __can__ see the original referrer if the referrer policy allows it, right?

What I'm talking about is the referrer policy passed to the service worker and the referrer calculation running in the service worker if the script calls `fetch` on the passed request.


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/266#issuecomment-203883782