fix(wopi): rate limit wopi endpoints#5606
Merged
Merged
Conversation
Collaborator
Author
|
/backport to stable33 please |
Collaborator
Author
|
/backport to stable32 |
AndyScherzinger
approved these changes
Apr 29, 2026
elzody
force-pushed
the
fix/brute-force-version-history
branch
from
44122a6 to
2afa1d0
Compare
elzody
changed the title
Uses a new rate limiter service to rate limit certain WOPI endpoints via the WOPI token. This attempts to prevent abuse when a token tries to spam requests. Signed-off-by: Elizabeth Danzberger <elizabeth@elzody.dev>
elzody
force-pushed
the
fix/brute-force-version-history
branch
from
2afa1d0 to
c5a9010
Compare
This was referenced Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The intention is to prevent someone editing with a guest token from abusing the
checkFileInfoandgetFileendpoints via rate limiting. The rate limiting is implemented in a service that handles it on a per-token basis. Additionally, guest users should not be able to request previous versions of a file since they do not have access to version history in the UI, so those requests are blocked.