Re: [ServiceWorker] Define some way for foreign fetch to decide on opaqueness of responses (#841)

> Wait, why would `event.request.origin` match `location.origin`? I don't think it should. 

If `example.com` makes a request for `https://fonts.example.com/foo.woff` then `request.origin` is `https://fonts.example.com`.

Since `foreignfetch` events can only handle requests made to the registration's origin, and SW scripts can only be same origin, `location.origin` within the SW handling a `foreignfetch` for a request with url `https://fonts.example.com/foo.woff` must be `https://fonts.example.com`.

(bracing myself for having a fundamental misunderstanding of foreign fetch)

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/841#issuecomment-188720288