Re: [fetch] Mechanism to indicate "destination context" (#64)

Referer: interesting. What would the UA send in iframe case vs the click? The fact that these are different is, by itself, seems rather odd to me.

Predicting type: you don't have to if you don't care about initialize appropriate request headers and such. E.g. if you want to prefetch an image, then you *do* want to advertise the fact that you support certain image types, and that Accept header is only added when we know we're requesting an image. As such, this is an opt-in hint to the UA.

Differentiating pre* vs non-pre: true, but as noted, it adds more complexity.

CSP: agree, but this is something that CSP itself needs to address. Today there is no CSP directive that controls existing prefetch/prerender deployments. I do think it's reasonable to add a directive to control these; the directive should be a new one, it can't be tied to anything that already exists. To me this is a non-blocking issue to what we're discussing here.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/64#issuecomment-120174795