- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Sat, 03 Aug 2024 23:31:29 +0000
- To: public-css-archive@w3.org
The current rate limits are somewhat arbitrary and can certainly be adjusted if regular users are hitting them. It's a matter of finding a balance between patterns of normal use and badly behaving bots, which are constantly hitting the server and were sucking up an obscene amount of resources before the current rate limit/ban system went into effect. In general the limits are 1 request/second over a 10 minute window, with bursts allowed over short periods to fetch linked resources. The burst rate is higher for image folders, but in theory, a single spec loading over 200 resources could trigger a rate limit. Note that when a rate limit is hit, the server starts returning 429 codes, so a well-behaved bot should back off. It's only when rate limits are triggered multiple times over a short period that the IP ban comes into effect. For your incident, you hit 6 rate limits over 13.5ms (likely just too many resources for a single spec). I just bumped the burst limit for images to 300. Also note that bans are cumulative, e.g. 4 hours for first ban, 8 for second, 12 for third, etc. We currently have some offenders at 92 hour bans, and thanks to CrowdSec's blocklists we're currently blocking 52634 known bad IPs. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5556#issuecomment-2267193583 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 3 August 2024 23:31:30 UTC