2019-12-21 20:55:43 +05:30
---
2021-01-29 00:20:46 +05:30
stage: none
group: unassigned
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/#designated-technical-writers
2019-12-21 20:55:43 +05:30
type: reference
---
# Protected paths **(CORE ONLY)**
2020-04-22 19:07:51 +05:30
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-12-21 20:55:43 +05:30
2020-03-13 15:44:24 +05:30
```plaintext
2019-12-21 20:55:43 +05:30
'/users/password',
'/users/sign_in',
'/api/#{API::API.version}/session.json',
'/api/#{API::API.version}/session',
'/users',
'/users/confirmation',
'/unsubscribes/',
2020-01-01 13:55:28 +05:30
'/import/github/personal_access_token',
'/admin/session'
2019-12-21 20:55:43 +05:30
```
GitLab responds with HTTP status code `429` to POST requests at protected paths
that exceed 10 requests per minute per IP address.
This header is included in responses to blocked requests:
2020-03-13 15:44:24 +05:30
```plaintext
2019-12-21 20:55:43 +05:30
Retry-After: 60
```
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-03-13 15:44:24 +05:30
> Introduced in [GitLab 12.4](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/31246).
2019-12-21 20:55:43 +05:30
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` .
