First version for Omeka Classic, the counterpart of Traffic Guard 1.0 for Omeka S.
- Checks every public request when Omeka has loaded its plugins, before routing and before any page is built: the allowlist, bans, a per-address count in one-minute windows and a risk score. Slowed-down requests get a 429 with
Retry-After: 60, blocked ones a 403. Any error lets the request through. - Kinds of page with their own limits, for Classic's paths: searches (the search page, the advanced search form, and keyword or field searches of browse pages), record pages (items, collections, files, exhibits), the REST API, MCP Server (its endpoint and OAuth discovery documents), and all other pages. The admin is never limited.
- Risk scoring as in the Omeka S module: user-agent rules, empty and known bot user agents (not held against MCP clients), going near or over a limit, deep paging and oversized searches, weighted per mode.
- Protection modes Normal, Elevated and Under attack, each with its own limits, scores and weights, all editable.
- Bans: automatic on a block for a set time, manual by Super Users for hours or with no end, with a note; lifted with one click.
- User-agent rules (text or regular expression, allow or block, by priority, on or off) and an allowlist of addresses and IPv4/IPv6 ranges, plus private networks allowed automatically.
- Dashboard: the last 24 hours, a filterable event log with the signals behind each decision, the most blocked addresses, active bans, and each address's history and counts. Super Users and Admins see it; only Super Users ban.
- Cleanup: old events and stale counters are pruned as requests come in, or at once from the dashboard.