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

Authorisation failure (401) masked by 502 from Nginx #45

Open
grahammcculloch opened this issue Sep 3, 2019 · 1 comment
Open

Authorisation failure (401) masked by 502 from Nginx #45

grahammcculloch opened this issue Sep 3, 2019 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@grahammcculloch
Copy link
Collaborator

Apparently if we make a POST request and the Node.js server responds with 401 because the user's session has expired, the Nginx server just responds with 502 to the client so the mobile app doesn't know that we need to log in again.

This results in some upload failures that confuse the user.

@grahammcculloch grahammcculloch added the bug Something isn't working label Sep 3, 2019
@grahammcculloch grahammcculloch added this to the v1.5.4 milestone Sep 3, 2019
@grahammcculloch grahammcculloch self-assigned this Sep 3, 2019
@grahammcculloch
Copy link
Collaborator Author

I'm going to try to mitigate this issue by checking the session whenever the app is foregrounded. If the session is about to expire, we'll return to the login page. Its unlikely that anyone will keep the app in the foreground for long enough for the session to expire while they're using the app in the foreground!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant