You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed
The Worker's rate limit runs on Cloudflare's Rate Limiting binding. It
is the same 30 requests per 10 seconds per reader on /api/*, counted
inside Cloudflare instead of in the app's storage, so a request no longer
costs a storage write. It is checked once, before the cache and the bot
check, so every API route and every repeated answer counts toward it.
Pages the Worker renders are limited too, such as a page that does not
exist: 30 per 10 seconds per reader, on an allowance of their own, answered
with 429 and retry-after. Pages and files served as they were built are
not affected.
An IPv6 reader counts as its /64, so moving between addresses in one
household's range no longer buys a fresh limit.
The zone's rate-limiting rule is now one a free zone can set: /api/*,
60 requests per 10 seconds per IP, blocked for 10 seconds. docs/self-hosting.md has the steps.
Fixed
A block by the zone's rule reads as "too many requests". Cloudflare
answers it with its own page rather than the app's JSON, and the app took
that for a broken answer: tiles kept their own retry schedule, the feed
reader's queue did not pause, and the one notice did not appear.