-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
200 returned on net::ERR_CONNECTION_REFUSED #14
Comments
Thanks for the report. |
So this is patched in 8245929. Released as Note that nanoajax doesn't do much for you in this case, still giving you a callback with |
Thanks, that will work for my use case. |
@kjk I was thinking about this again, and realized that nanoajax could call back with |
@yanatan16 sounds like a good idea, thanks! |
This is Chrome 47.0.2526.106 (64-bit) on Mac.
When testing locally and when the server is not running, a request callback has code = 200 and empty responseText.
This issue is here:
In my case
req.status
is 0 but is converted to 200 (statusCode
) because it's called from:if (req.readyState === 4) success()
. In console I see 'net::ERR_CONNECTION_REFUSED' error.Not sure what cases are where req.status 0 should be converted to something else. It seems to me this should be reported as error i.e. req.status should be passed as is to the callback.
The text was updated successfully, but these errors were encountered: