Follow-up from "Add rate limit docs"
The following discussions from !30829 (merged) should be addressed:
-
@eread started a discussion: for simpler limits that are configured in UI.
-
@eread started a discussion: NOTE: **Note:** Starting with GitLab 11.2, Rack Attack is disabled by default. If your
To avoid any ambiguity.
-
@eread started a discussion: - Protected paths will be throttled. - Failed authentications for Git and container registry requests will trigger a temporary IP ban.
These can take periods.
-
@eread started a discussion: GitLab responds with HTTP status code `429` to POST requests at protected paths
Nitpick.
-
@eread started a discussion: - User sign-in - User sign-up (if enabled) - User password reset
Our usual style.
-
@eread started a discussion: GitLab responds with HTTP status code `403` for 1 hour, if 30 failed
Nitpick.
-
@eread started a discussion: GitLab.com responds with HTTP status code `429` to API requests over 10 requests
Nitpick.
-
@eread started a discussion: Strong preference to not run a section heading immediately after a parent section heading.
Even a single sentence to describe what's next is useful.
-
@eread started a discussion: GitLab.com responds with HTTP status code `429` to POST requests at protected
Nitpick.
-
@eread started a discussion: GitLab.com responds with HTTP status code `403` for 1 hour, if 30 failed
Nitpick.
-
@eread started a discussion: [GitLab.com-specific rate limits](../user/gitlab_com/index.md#gitlabcom-specific-rate-limits).