diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-11-04 03:13:32 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-11-04 03:13:32 +0000 |
| commit | 96e9edba8a8898045daca33ae7dc3f03aa5b0677 (patch) | |
| tree | 282e0acccde9ba825e873cc865b2b9966aa91eaa /doc/security/rate_limits.md | |
| parent | 4e86ca506d67f27cb4ca93b47efc53adc1c237a6 (diff) | |
| download | gitlab-ce-96e9edba8a8898045daca33ae7dc3f03aa5b0677.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/security/rate_limits.md')
| -rw-r--r-- | doc/security/rate_limits.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/security/rate_limits.md b/doc/security/rate_limits.md index 3826c02a201..9d49297c9de 100644 --- a/doc/security/rate_limits.md +++ b/doc/security/rate_limits.md @@ -27,7 +27,7 @@ Most cases can be mitigated by limiting the rate of requests from a single IP ad Most [brute-force attacks](https://en.wikipedia.org/wiki/Brute-force_attack) are similarly mitigated by a rate limit. -## Admin Area settings +## Configurable limits You can set these rate limits in the Admin Area of your instance: @@ -42,6 +42,10 @@ You can set these rate limits in the Admin Area of your instance: - [Files API rate limits](../user/admin_area/settings/files_api_rate_limits.md) - [Deprecated API rate limits](../user/admin_area/settings/deprecated_api_rate_limits.md) +You can set these rate limits using the Rails console: + +- [Webhook rate limit](../administration/instance_limits.md#webhook-rate-limit) + ## Failed authentication ban for Git and container registry GitLab returns HTTP status code `403` for 1 hour, if 30 failed authentication requests were received |