diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-19 03:07:13 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-19 03:07:13 +0300 |
commit | a94adeb6b2b212e824d1bbce5da16ecd7d1b5a20 (patch) | |
tree | 6d5be7275e6f5aec9888758b81318cb8648c3c17 /doc/development/application_limits.md | |
parent | 355a4a17ebbeb246e48954462163577ae77f45c0 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/application_limits.md')
-rw-r--r-- | doc/development/application_limits.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/application_limits.md b/doc/development/application_limits.md index b1efc11db62..40d157a4411 100644 --- a/doc/development/application_limits.md +++ b/doc/development/application_limits.md @@ -171,7 +171,7 @@ The process for adding a new throttle is loosely: 1. Extend `Gitlab::RackAttack` and `Gitlab::RackAttack::Request` to configure the new rate limit, and apply it to the desired requests. 1. Add the new settings to the Admin Area form in `app/views/admin/application_settings/_ip_limits.html.haml`. -1. Document the new settings in [User and IP rate limits](../user/admin_area/settings/user_and_ip_rate_limits.md) and [Application settings API](../api/settings.md). +1. Document the new settings in [User and IP rate limits](../administration/settings/user_and_ip_rate_limits.md) and [Application settings API](../api/settings.md). 1. Configure the rate limit for GitLab.com and document it in [GitLab.com-specific rate limits](../user/gitlab_com/index.md#gitlabcom-specific-rate-limits). Refer to these past issues for implementation details: |