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

Understand "426 Upgrade Required" on API calls #1254

Closed
nickvergessen opened this issue May 30, 2023 · 2 comments · Fixed by #1291
Closed

Understand "426 Upgrade Required" on API calls #1254

nickvergessen opened this issue May 30, 2023 · 2 comments · Fixed by #1291
Assignees

Comments

@nickvergessen
Copy link
Member

With an upcoming server change, it will be possible to enforce a minimum client version:

This requires all future clients to be able to understand 426 Upgrade Required. Ideally they should:

  • Show a note to the user that the client is too old and no longer supported by the server.
  • Have a "button of action" allowing the user to get to the update as quick as possible (link to iOS Appstore / Google Play Store / Desktop download page)
  • Clients should pause making further requests to not DoS attack the server in an attempt to get a room list, etc.
@SystemKeeper
Copy link
Collaborator

  • Have a "button of action" allowing the user to get to the update as quick as possible (link to iOS Appstore / Google Play Store / Desktop download page)

This might be tricky for branded clients, we might want to disable that for them I guess.

@nickvergessen
Copy link
Member Author

I think branding hands in a Appstore URL. But yeah otherwise just replace the button with an "Ok"

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

Successfully merging a pull request may close this issue.

3 participants