408 Request Timeout ( RFC7231 )
The origin server did not receive the complete request in what it considers a reasonable time.
- Implied the server does not wish to wait and continue the connection.
- Not used much because servers typically choose to use the “close” connection option.
429 Too Many Requests ( RFC6585 )
Client has sent too many requests in the specified amount of time according to the server. Often known as “rate-limiting”. Server may respond with information allowing the requester to retry after a specific period of time.
Cloudflare will generate and send this status code when a request is being rate limited. If visitors to your site are receiving these error codes, you will be able to see this in the Rate Limiting Analytics.
Error 1015: You are being rate limited
The site owner implemented Rate Limiting that affects your visitor traffic.
Unable to purge is another 1015 error code relating to Cloudflare cache purge. Retry the cache purge and contact Cloudflare support if errors persist.
- If you are a site visitor, contact the site owner to request exclusion of your IP from rate limiting.
- If you are the site owner, review Cloudflare Rate Limiting thresholds and adjust your Rate Limiting configuration.
- If your Rate Limiting blocks requests in a short time period (i.e. 1 second) try increasing the time period to 10 seconds.
If you expect a new Cloudflare Worker to exceed rate limits, refer to the Workers documentation for guidance.
May I request the link to what website this is having an issue on? Let’s see which error I get! I hope I can help!