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

Set max req count before applying rate limit #474

Merged
merged 1 commit into from
Apr 8, 2024
Merged

Conversation

DrizzlyOwl
Copy link
Collaborator

  • Exposes a variable that can be adjusted to raise or lower the threshold of incoming requests before a WAF rate limit is applied.
  • The container app module sets the time range to 1 minute, so with this default value there must be at least 300reqs/min before a rate limit is applied.
  • This mirrors the same default as is set in the container app module
  • This will likely be raised in Production when we have real-world traffic consuming the API.

@DrizzlyOwl DrizzlyOwl requested a review from Stretch96 April 8, 2024 13:41
* Exposes a variable that can be adjusted to raise or lower the threshold of incoming requests before a WAF rate limit is applied
@DrizzlyOwl DrizzlyOwl merged commit 83a8cec into main Apr 8, 2024
1 of 2 checks passed
@DrizzlyOwl DrizzlyOwl deleted the waf-rate-limit branch April 8, 2024 13:50
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