Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272)

> Incidentally, if a service worker does fetch(foreignFetchEvent.request), does the fetch() use the foreign origin or is it coerced to the service worker's origin somehow?

That's a very good question... As currently spec'ed I believe it is coerced to the service worker's origin. The `fetch()` method invokes the `Request` constructor with the arguments passed to it, which causes a new request to be created that is mostly identical to the request passed in, but with origin set to "client" (and possibly a few other differences as well). As spec'ed it would keep the original referrer though (so referrer and origin won't match). I think this all works out the way I would expect it (the fetch from the service worker being same origin, I think the fetch algorithms would do the right thing).

---
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/272#issuecomment-205890025