IE9 fix for cross domain calls

[ruchigoyal2005]

This pull request includes these fixes for IE9:

1. Fixed axios promise rejection on request onload for cors api calls.
2. Fixed cors api calls timing out prematurely.

[nettofarah]

I'm assuming that this works in all browsers (because travis is passing)
but have you manually checked this in other browsers too?

Also, can I suggest that you rewrite your commit message to make it a little more clear?
Here's a great guide on how to write good commit messages: http://chris.beams.io/posts/git-commit/

[ruchigoyal2005]

I tested this change manually in Chrome/firefox/IE9/IE10/IE11. I updated the commit message. thanks for the suggestion !!!

[mzabriskie]

fixes #240

[mzabriskie]

How does this work with the reference to request.responseText? This seems really strange to get the response from the request.

[ruchigoyal2005]

Request is XDomainRequest and it has responseText property which retrieves the response body as a string.
https://msdn.microsoft.com/en-us/library/cc288060(v=vs.85).aspx

[mzabriskie]

It's only XDomainRequest if it exists, otherwise it's XMLHttpRequest. Will it still work in both scenarios?

[ruchigoyal2005]

@mzabriskie : For XMLHttpRequest we do get the response status. This scenario exists only for XDomainRequest. If you see this condition:

((response.status >= 200 && response.status < 300) ||
(!('status' in request) && request.responseText) ?
resolve :
reject)(response);

In 1st condition response status getting checked. For XMLHttpReuqest this 1st condition gets executed. For XDomainRequest we don't get the status in the response, that's why we need to check the request.responseText.

[ruchigoyal2005]

Can you please merge this pull request if it looks ok ?..thanks !

[mzabriskie]

Thank you for your PR!

[nickuraltsev]

@ruchigoyal2005 @mzabriskie I'm still curious why this code rejects the promise in case when request.responseText is empty. For example, it's common to return an empty response body for successful PUT and DELETE requests.