Re: [whatwg/fetch] CH processing, cross-origin redirects and service workers (#800)

First, for context, per current plan we will use [Feature Policy to enable CH delegation](https://github.com/WICG/feature-policy/issues/129). Under that model, 1P will have to explicitly delegate delivery of CH to 3P origins; CH hints will not be sent to 3P origins by default.

So, above question should be (re)scoped to: if a CH-whitelisted origin redirects to a non-whitelisted origin, what's the behavior we expect — correct?

If so, I think the answer should be that CH headers are stripped on such redirects because the destination origin is not on the whitelist. Any reasons for why this shouldn't be the case?

---

I'm not sure I follow why SW wouldn't see these headers? We definitely *do* want SW to see them, as they can and should be used to do resource selection + caching when doing CH content negotiation.




-- 
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/800#issuecomment-415651429