Re: [fetch] Status code to use in a response indicating rejection of a cross-origin access (#172)

No @tyoshino is asking what a server should do if it implements CORS and does not want to give a normal response to a given request. However, as he pointed out the server cannot distinguish a CORS request from other requests since `Origin` can be used for either.

It seems in such scenarios the server can use 400 or 403, but I'm not sure the specification needs to say anything since the client will not act on it necessarily.

(As far as any APIs are concerned whenever the CORS protocol is not honered it is a network error which has a status of 0.)

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