CORS Error Response Status = 0

[tysonnero]

I'm using Angular 1.0.6.

It seems whenever a CORS request fails, the response returned is always 0.

I am not using JSONP.

[danielzen]

I'm having this issue as well with the same version: 1.0.6.
Also not using JSONP

[pkozlowski-opensource]

@tysonnero @danielzen I'm afraid that this is what we are getting from a browser's XHR object. Closing for now, please reopen if you believe that there are improvements that could be done on AngularJS side in this respect.

[tysonnero]

I've done a little research and it seems like people are experiencing in the case of the client code handling the response incorrectly or the server not setting the proper headers. I will see if I can remedy this on the server side.

Also, some recommend to migrate to JSONP, but I noticed there is the same issue open for JSONP within Angular.

[lucipacurar]

I'm having the same problem. The server replies with status 401 but my request interceptor says the status is 0.

[okonon]

same issue as @lucassp. Did you ever figure it out?

[lucipacurar]

@okonon yes, all server responses must have the CORS headers attached, even 4xx, 5xx responses, so that the browser parses them.

[MartinhoMCM]

I solved this problem studying HTTP Responses.
The problem was the HTTP code that my server returned was incorrect, I mean I don't use the right way. When the server returns a wrong HTTP code it can create a problem with the browser.