Re: [whatwg/fetch] Allow custom headers on no-cors requests (#380)

So, when the fetch spec was originally written it had a lot of "if a request is created with a potentially bad condition throw or discard some bad bits immediately" type logic.  Lately we have moved towards waiting to trigger the error handling until the request actually ends up trying to trigger a cross-origin request.

For example, #663 does not forbid "manual" redirect mode for "no-cors" requests.  It just makes any such fetch that goes cross-origin reject.

The suggestion in https://github.com/whatwg/fetch/issues/380#issue-174581060 seems consistent with this approach.  The request can be created and function with full features for same-origin URLs.  When it goes cross-origin the data is stripped (or we could reject).

-- 
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/380#issuecomment-382842035