2019-10-01 08:05:59 -04:00
---
2020-10-29 17:08:54 -04:00
stage: none
group: unassigned
2020-11-26 01:09:20 -05:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2019-10-01 08:05:59 -04:00
type: reference
---
2021-01-28 01:08:59 -05:00
# Protected paths **(FREE SELF)**
2019-10-01 08:05:59 -04:00
2020-03-20 20:09:18 -04:00
Rate limiting is a common technique used to improve the security and durability
of a web application. For more details, see
[Rate limits ](../../../security/rate_limits.md ).
GitLab rate limits the following paths with Rack Attack by default:
2019-10-01 08:05:59 -04:00
2020-01-30 01:08:49 -05:00
```plaintext
2019-10-01 08:05:59 -04:00
'/users/password',
'/users/sign_in',
'/api/#{API::API.version}/session.json',
'/api/#{API::API.version}/session',
'/users',
'/users/confirmation',
'/unsubscribes/',
2019-12-02 07:06:45 -05:00
'/import/github/personal_access_token',
'/admin/session'
2019-10-01 08:05:59 -04:00
```
GitLab responds with HTTP status code `429` to POST requests at protected paths
that exceed 10 requests per minute per IP address.
2021-01-07 16:10:18 -05:00
See [User and IP rate limits ](../../admin_area/settings/user_and_ip_rate_limits.md#response-headers ) for the headers responded to blocked requests.
2019-10-01 08:05:59 -04:00
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.
## Configure using GitLab UI
2020-02-09 19:09:07 -05:00
> Introduced in [GitLab 12.4](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/31246).
2019-10-01 08:05:59 -04:00
Throttling of protected paths is enabled by default and can be disabled or
customized on **Admin > Network > Protected Paths** , along with these options:
- Maximum number of requests per period per user.
- Rate limit period in seconds.
- Paths to be protected.
Requests over the rate limit are logged into `auth.log` .
