-
-
Notifications
You must be signed in to change notification settings - Fork 756
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
client-side onError() function is not fired as expected when the client can not connect the server. #963
Comments
Fixed. Try it and let me know what you think. I've improved the error message (_response.status). |
sorry, this fix does not work well. but the test result is: when subscribing using long-polling, the server return:
which should not trigger neither the onOpen() method nor onMessage() method. please check again. |
And what I want to do is to detect whether the client is connected the server or not. best regards, |
This is the expected behavior right now, e.g only error code larger than 500 will fire the onError. This behavior never changed, e.g atmosphere.js always allowed the onMessage() to be invoked. Please file another issue and I will see if I want to change the default behavior with 1.0.x . Thanks |
the bug happened when the transport is long-polling. to reproduce it, just set the request.url to a nonexistent one.
more details to see:
https://groups.google.com/forum/#!topic/atmosphere-framework/eV4rFSbpZH0
The text was updated successfully, but these errors were encountered: