gitlab-ce/doc/administration/settings/protected_paths.md

stage, group, info, type

stage	group	info	type
none	unassigned	To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments	reference

Protected paths (FREE SELF)

Rate limiting is a technique that improves the security and durability of a web application. For more details, see Rate limits.

You can rate limit (protect) specified paths. For these paths, GitLab responds with HTTP status code 429 to POST requests that exceed 10 requests per minute per IP address and GET requests that exceed 10 requests per minute per IP address at protected paths.

For example, the following are limited to a maximum 10 requests per minute:

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

After 10 requests, the client must wait 60 seconds before it can try again.

See also:

• List of paths protected by default.
• User and IP rate limits for the headers returned to blocked requests.

Configure protected paths

Introduced in GitLab 12.4.

Throttling of protected paths is enabled by default and can be disabled or customized.

1. On the left sidebar, expand the top-most chevron ({chevron-down}).
2. Select Admin Area.
3. Select Settings > Network.
4. Expand Protected paths.

Requests that exceed the rate limit are logged in auth.log.