Measured on production after the 4.5.0 deploy: with a new connection per request, 1,000 requests in 53 s got no 429 from RL_SITE (120/60 s); over one keep-alive connection, 429 after ~93. The ratelimits binding counts per machine of a data centre and syncs late, so the zone's WAF rule is the limit that holds against floods. Verified once the owner set the rule (300/10 s): 800 requests in 4.9 s gave 111 x 200, 201 x Worker 429 and 488 x WAF 1015, with the site answering again 10 s later. Runbook test commands, code comments, CLAUDE.md gotcha 43, the 4.5.0 changelog entry. [skip-discuss] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
Changelog — 4.5.x
Release notes for 4.5.0, newest first. Every version: CHANGELOG.md.
[4.5.0] - 2026-10-27 (Rate limits for the whole site)
The website now limits how many requests one connection can send in a short time, on every page, cover image and API address — not only on the Suggest form and the verification check. Normal browsing never comes close to the limits; a script that floods the site gets HTTP 429 ("Too many requests") and has to wait a minute. Nothing changes in the desktop and Android apps.
Upgrade notes
- Nothing to accept again: no policy changed. The Privacy Policy already says that your IP address is used, without being stored, to count requests and limit abuse.
- Desktop and Android apps: install 4.5.0 over 4.4.3 as usual; they don't use the limited addresses (4.0–4.1.1 count against the site limit when they read the old catalog files).
Added
- Per-connection limits in the Worker: every request that runs the site's server code counts, per minute and per address (an IPv6 connection by its /64): 120 for pages, the public API and the catalog files of the old apps, 600 for cover images (a Games page shows up to 100), 300 for the admin. The Suggest form (5 a minute) and the verification check (20 a minute) keep their own, stricter limits on top. Search engines that Cloudflare has verified are not counted.
- The "Too many requests" answer: pages get a short page in English or Vietnamese (no scripts),
the API and cover images a JSON
{"error":"rate_limited"}; both say when to retry (Retry-After: 60) and are never cached. The admin shows "Too many requests from this connection". - A first layer in front of the Worker: the maintainer's runbook (
docs/operations.md, section 1 step 15) sets up a Cloudflare WAF rate-limiting rule that blocks floods before they reach the site's code, and covers the static files the Worker never sees. The Worker's own counts are approximate (Cloudflare counts them per server and syncs them late), so the WAF rule is what holds against a flood that opens a new connection for every request.
Fixed
- Suggest and verification limits counted other sites too: a rate limit's namespace is shared by every Worker of the Cloudflare account, and the two existing limits used the same numbers as other Workers there, so their visits could use up this site's Suggest or verification allowance. All of this site's limits now have namespaces of their own.
Changed
- Security policy: says how the site limits requests (EN + VI); no new obligations.