Commit 5e7d85af authored by Jacob Vosmaer's avatar Jacob Vosmaer

Apply 5 suggestion(s) to 1 file(s)

parent b29342cd
...@@ -514,8 +514,8 @@ code. The client should wait before attempting the request again. There ...@@ -514,8 +514,8 @@ code. The client should wait before attempting the request again. There
are also informational headers with this response detailed in [rate are also informational headers with this response detailed in [rate
limiting responses](#rate-limiting-responses). limiting responses](#rate-limiting-responses).
GitLab.com's rate limits are changing in January 2021. The table below The following table describes the rate limits for GitLab.com, both before and
contains the limits that apply before and after this change. after the limits change in January, 2021:
| Rate limit | Before 2021-01-18 | From 2021-01-18 | | Rate limit | Before 2021-01-18 | From 2021-01-18 |
|:--------------------------------------------------------------------------|:----------------------------|:------------------------------| |:--------------------------------------------------------------------------|:----------------------------|:------------------------------|
...@@ -534,7 +534,7 @@ endpoints](../../user/admin_area/settings/rate_limits_on_raw_endpoints.md). ...@@ -534,7 +534,7 @@ endpoints](../../user/admin_area/settings/rate_limits_on_raw_endpoints.md).
The [`Retry-After` The [`Retry-After`
header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After) header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After)
will indicate when the client should retry. indicates when the client should retry.
In the case that a rate limit is applied by HAProxy, rather than In the case that a rate limit is applied by HAProxy, rather than
Cloudflare or the GitLab application, there will instead be Cloudflare or the GitLab application, there will instead be
...@@ -558,12 +558,12 @@ See [Protected Paths](../admin_area/settings/protected_paths.md) for more detail ...@@ -558,12 +558,12 @@ See [Protected Paths](../admin_area/settings/protected_paths.md) for more detail
### IP blocks ### IP blocks
IP blocks usually happen when GitLab.com receives unusual traffic from a single IP blocks can occur when GitLab.com receives unusual traffic from a single
IP address that the system views as potentially malicious based on rate limit IP address that the system views as potentially malicious, based on rate limit
settings. After the unusual traffic ceases, the IP address is automatically settings. After the unusual traffic ceases, the IP address is automatically
released depending on the type of block, as described below. released depending on the type of block, as described in a following section.
If you receive a `403 Forbidden` error for all requests to GitLab.com, please If you receive a `403 Forbidden` error for all requests to GitLab.com,
check for any automated processes that may be triggering a block. For check for any automated processes that may be triggering a block. For
assistance, contact [GitLab Support](https://support.gitlab.com/hc/en-us) assistance, contact [GitLab Support](https://support.gitlab.com/hc/en-us)
with details, such as the affected IP address. with details, such as the affected IP address.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment