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

If I understand the redirect behavior correctly, there are cases where the current behavior is less restrictive.

Assume request's original referrer is https://example.com/example.html.
Assume request's referrer policy is null.

|request URL|main page's referrer policy| SW's referrer policy|referer (existing)|referer (update the policy)|
|---|---|---|---|---|
|https://example.com/example.html|null|no-referrer|no-referrer|no-referrer|
|https://example.com/example.html|origin only|no-referrer|no-referrer|https://example.com/|
|https://example.com/example.html|origin only when cross-origin|no-referrer|no-referrer|https://example.com/example.html|
|https://example.com/redirect.html => https://example2.com/example.html|null|origin only when cross-origin|https://example.com/|https://example.com/|
|https://example.com/redirect.html => https://example2.com/example.html|origin only when cross-origin|null|https://example.com/example.html|https://example.com/|
|https://example.com/redirect.html => http://example.com/example.html|origin only when cross-origin|null|no-referrer|https://example.com/|
|https://example.com/redirect.html => http://example.com/example.html|no referrer when downgrade|unsafe URL|https://example.com/example.html|no-referrer|
|https://example.com/redirect.html => http://example.com/example.html|no referrer when downgrade|origin only|https://example.com/|no-referrer|

---
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-203732719