Re: [whatwg/fetch] fetch() doesn't properly handle errors from pre-flight responses with CORS (#443)

I absolutely understand what you are saying. A pre-flight response and the normal http response can be made. That's exactly how CORS works now. We were hoping to bypass the second http response by providing a code back from the pre-flight response. This will save the second http response for an uncountable amount of http requests. I understand this may be something that you don't want to consider. That is fine. I'm just trying to suggest that developers may want to be able to exert more control over how CORS works.

If it's not something whatwg is open to, I'm happy to leave this thread as is.

-- 
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/443#issuecomment-269463338