rate-limiting
Adds an ops-side rate-limiting:query:status query handler for inspecting current bucket state; the actual request throttling is wired automatically by the dispatcher when any handler declares a rateLimit option (e.g. { per: 'user', limit: 3, windowSeconds: 60 }) or when you pass context.rateLimit to buildServer. Loading this feature is optional if you only need L3 per-handler rate limits and have no need for ops introspection.
Dependencies
Section titled “Dependencies”- Requires: none
- Activation: always on (not toggleable)