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

A request has an associated origin (usually the origin of the client that made the request). Currently for foreign fetch we expect the foreign fetch event handler to pass this origin to respondWith to explicitly expose the contents of the response to that origin. But the origin of a request isn't actually exposed to javascript. I could add an `origin` or `clientOrigin` attribute to `ForeignFetchEvent`, but maybe it makes more sense to expose this directly for all `Request` instances?

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