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

@mnot in " a status code to be generated by fetch if there's a cross-origin access failure? If so, 403 is definitely the right one." Are you suggesting that the fetch function locally should fake an HTTP status code?  That sounds to be like a bad idea -- the caller really needs to understand what went on.  Better surely to make a new series of client-side error code 600 series maybe and allocate them for different kinds of CORS failure.   Of course currently often the status code is 0 for cors problems, and the calling code has to guess what happened -- sometimes ending up wasting time implementing different alternative fall backs in turn.

---
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/172#issuecomment-236966686