Skip to content
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

For offline notifications, connection endpoint replies back 502 Bad Gateway response code to Router Endpoint instead of replying 404 Not Found #89

Closed
MaenMax opened this issue Dec 27, 2018 · 0 comments

Comments

@MaenMax
Copy link

MaenMax commented Dec 27, 2018

Connection endpoint replies back 502 Bad Gateway response code to Router Endpoint instead of replying 404 Not Found. When sending a notification while the browser is disconnected (offline), connection endpoint (or Rust websocket server), reports 502 to the Python router, a response code that is not expected by the router. In the original implementation, and in such scenario, router used to receive 404 from the Python connection node.

bbangert added a commit that referenced this issue Jan 3, 2019
Tests weren't passing because autopush had a dependency change for FCM.
This updates the travis test to pull down the current dependencies for
autopush for integration tests.

Closes #89
bbangert added a commit that referenced this issue Jan 3, 2019
Tests weren't passing because autopush had a dependency change for FCM.
This updates the travis test to pull down the current dependencies for
autopush for integration tests.

Closes #89
bbangert added a commit that referenced this issue Jan 3, 2019
Tests weren't passing because autopush had a dependency change for FCM.
This updates the travis test to pull down the current dependencies for
autopush for integration tests.

Closes #89
bbangert added a commit that referenced this issue Jan 3, 2019
Tests weren't passing because autopush had a dependency change for FCM.
This updates the travis test to pull down the current dependencies for
autopush for integration tests.

Closes #89
bbangert added a commit that referenced this issue Jan 3, 2019
Tests weren't passing because autopush had a dependency change for FCM.
This updates the travis test to pull down the current dependencies for
autopush for integration tests.

Closes #89
bbangert added a commit that referenced this issue Jan 3, 2019
Tests weren't passing because autopush had a dependency change for FCM.
This updates the travis test to pull down the current dependencies for
autopush for integration tests.

Closes #89
bbangert added a commit that referenced this issue Jan 3, 2019
Tests weren't passing because autopush had a dependency change for FCM.
This updates the travis test to pull down the current dependencies for
autopush for integration tests.

Closes #89
bbangert added a commit that referenced this issue Jan 3, 2019
Tests weren't passing because autopush had a dependency change for FCM.
This updates the travis test to pull down the current dependencies for
autopush for integration tests.

Closes #89
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant