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

feat(server): Enforce attachment size in rate limits #639

Merged
merged 2 commits into from
Jun 26, 2020

Conversation

jan-auer
Copy link
Member

Passes the combined size of all attachments in an envelope to the Redis rate limiter as quantity. As a result, either all attachments are retained or dropped atomically.

The LUA script now accepts a third argument per quota which is the quantity. Similarly, the RedisRateLimiter requires callers to pass a quantity in, which is supplied by EnvelopeLimiter.

@jan-auer jan-auer requested a review from a team June 26, 2020 10:29
@jan-auer jan-auer self-assigned this Jun 26, 2020
@jan-auer jan-auer merged commit f884ee0 into master Jun 26, 2020
@jan-auer jan-auer deleted the feat/redis-quantity branch June 26, 2020 11:44
jan-auer added a commit that referenced this pull request Jun 26, 2020
* master:
  feat(server): Enforce attachment size in rate limits (#639)
jan-auer added a commit that referenced this pull request Jul 2, 2020
* master:
  fix(server): Do not 429 for event-only attachments (#647)
  doc(config): Remove references to advanced data scrubbing (#648)
  fix(server): Never respond with 429 for minidumps (#646)
  docs(config): Update relay end user documentation (#641)
  license: Update BSL change date
  fix: Add missing .NET 4.8 patches (#642)
  feat(server): Emit attachment sizes to Kafka (#644)
  fix(store): Use clock drift normalizer to correct all timestamp issues  (#634)
  feat(server): Emit flags for rate limited attachments (#640)
  feat(server): Enforce attachment size in rate limits (#639)
  feat(server): Apply quotas per item (#636)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants