Re: [fetch] force-Origin-header flag set for no-cors requests (#91)

The change "force -> omit" and making the default to `unset` sounds ok.

----

Since it seemed many people were treating presence of "Origin" as indication whether or not the server has to handle CORS (see https://code.google.com/p/chromium/issues/detail?id=512836 ), it was not easy for us (and maybe also for Firefox) to change the XHR implementation conform to the spec.

Per Yutaka's post above, Firefox introduced `fetch()` being conforming to the spec. It's good opportunity. Chromium should also try to align our `fetch()` with it, I think.

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