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

Code 503 should mean down #89

Closed
ghplink opened this Issue Jul 22, 2014 · 4 comments

Comments

Projects
None yet
4 participants
@ghplink

ghplink commented Jul 22, 2014

Scenario: Apache HTTP server forwards requests to a tomcat web server. In case tomcat is down, the apache sends a 503 (server temporarily not available). Offline.js should recoginize that as down, instead it says up.

@adamschwartz

This comment has been minimized.

Show comment
Hide comment
@adamschwartz

adamschwartz Jul 22, 2014

Member

Offline.js provides an indication of network connectivity for the client, not the server.

Member

adamschwartz commented Jul 22, 2014

Offline.js provides an indication of network connectivity for the client, not the server.

@ghplink

This comment has been minimized.

Show comment
Hide comment
@ghplink

ghplink Jul 22, 2014

I partially disagree. Users (that means client side) should be informed correctly about the accessibility of 'their' application server (meaning the server with the business logic). In the scenario described this is the tomcat server. I think, state of technical network connectivity is not enough, neither for software clients nor end users.

ghplink commented Jul 22, 2014

I partially disagree. Users (that means client side) should be informed correctly about the accessibility of 'their' application server (meaning the server with the business logic). In the scenario described this is the tomcat server. I think, state of technical network connectivity is not enough, neither for software clients nor end users.

@zackbloom

This comment has been minimized.

Show comment
Hide comment
@zackbloom

zackbloom Jul 22, 2014

Member

You are very much encouraged to monitor the failure of requests you make, and inform the user accordingly. In fact, we have a library which makes it a bit easier: http://github.hubspot.com/messenger/

Offline is meant more for helping your user deal with losing their general internet connection.

Member

zackbloom commented Jul 22, 2014

You are very much encouraged to monitor the failure of requests you make, and inform the user accordingly. In fact, we have a library which makes it a bit easier: http://github.hubspot.com/messenger/

Offline is meant more for helping your user deal with losing their general internet connection.

@gustavomick

This comment has been minimized.

Show comment
Hide comment
@gustavomick

gustavomick May 11, 2016

sorry but i dont get it, why offlinejs cant provide both solutions (sever and client check)?
what about adding response.status to result event like confirmed-up / confirmed-down or better create confirmed event with http status and let use it.
nice lib thanks.

gustavomick commented May 11, 2016

sorry but i dont get it, why offlinejs cant provide both solutions (sever and client check)?
what about adding response.status to result event like confirmed-up / confirmed-down or better create confirmed event with http status and let use it.
nice lib thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment