You need to sign in or sign up before continuing.

Follow-up from "Add rate limit docs"

The following discussions from !30829 (merged) should be addressed:

for simpler limits that are configured in UI.

NOTE: **Note:** Starting with GitLab 11.2, Rack Attack is disabled by default. If your

To avoid any ambiguity.

- Protected paths will be throttled.
- Failed authentications for Git and container registry requests will trigger a temporary IP ban.

These can take periods.

GitLab responds with HTTP status code `429` to POST requests at protected paths

Nitpick.

- User sign-in
- User sign-up (if enabled)
- User password reset

Our usual style.

GitLab responds with HTTP status code `403` for 1 hour, if 30 failed

Nitpick.

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.

GitLab.com responds with HTTP status code `429` to POST requests at protected

Nitpick.

GitLab.com responds with HTTP status code `403` for 1 hour, if 30 failed

Nitpick.

[GitLab.com-specific rate limits](../user/gitlab_com/index.md#gitlabcom-specific-rate-limits).