feat(security): Allow to opt-out of ratelimit protection, e.g. for te… #37542
Conversation
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
ChristophWurst
approved these changes
Apr 3, 2023
juliusknorr
reviewed
Apr 3, 2023
juliusknorr
approved these changes
Apr 3, 2023
…sting on CI Signed-off-by: Joas Schilling <[email protected]>
nickvergessen
force-pushed
the
bugfix/noid/allow-to-opt-out-of-ratelimit-for-testing
branch
from
74c6ae9 to
454281a
Compare
Member
Author
|
/backport to stable26 |
Member
Author
|
/backport to stable25 |
Member
Author
|
/backport to stable24 |
Member
Author
|
/backport to stable23 |
Member
Author
|
/backport to stable22 |
nickvergessen
deleted the
bugfix/noid/allow-to-opt-out-of-ratelimit-for-testing
branch
5 tasks
This was referenced Apr 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…sting on CI
Summary
On talk integration tests are red on CI since middle of last week (Merge of #37497 ). Turns out it's the rate limiting hitting in disallowing to set the user's display name. See nextcloud/spreed#9233 for debugging history.
Checklist