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.

Sign up for GitHub

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

Jump to bottom

Blocking older clients - Understand "426 Upgrade Required" on API calls #9660

Closed
4 tasks done
nickvergessen opened this issue May 30, 2023 · 1 comment
Closed
4 tasks done

Blocking older clients - Understand "426 Upgrade Required" on API calls #9660

nickvergessen opened this issue May 30, 2023 · 1 comment
Labels
1. to develop enhancement overview
Milestone
v17.1.0-rc.2

Comments

@nickvergessen
Copy link
Member

nickvergessen commented May 30, 2023 •
edited
Loading

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.
@nickvergessen nickvergessen added this to the 💜 Next Major (28) milestone May 30, 2023
@Antreesy Antreesy mentioned this issue Aug 9, 2023
Closed
6 tasks
@nickvergessen
Copy link
Member Author

All done 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1. to develop enhancement overview
Projects
💬 Talk team
Archived in project
Milestone
v17.1.0-rc.2
Development

Successfully merging a pull request may close this issue.

Redirect desktop client when 426 response is received nextcloud/spreed
1 participant
@nickvergessen