-
Notifications
You must be signed in to change notification settings - Fork 0
feat(server): add rate limiting middleware #91
Copy link
Copy link
Open
Labels
featrequest for or implementation of a new featurerequest for or implementation of a new featuregood first issuesimple and well-defined issue, good for newcomerssimple and well-defined issue, good for newcomersservernvisy-server: API handlers, middleware, authnvisy-server: API handlers, middleware, auth
Description
Context
The server does not enforce per-client or per-tenant rate limits. Rate limiting is required for API hardening and is called out in the runtime's INFRASTRUCTURE.md.
Requirements
- Middleware-based rate limiting with configurable thresholds
- Per-client (API token or session) and per-workspace tracking
- Configurable limits per endpoint category:
- Authentication endpoints: stricter limits to prevent brute-force
- File upload and job dispatch: throughput-based limits
- Read endpoints: higher allowances
- Return
429 Too Many RequestswithRetry-Afterheader - Rate limit state storage (in-memory or Redis-backed for multi-instance deployments)
References
- Server docs: SECURITY.md - Rate Limiting
- Runtime: INFRASTRUCTURE.md Section 3
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
featrequest for or implementation of a new featurerequest for or implementation of a new featuregood first issuesimple and well-defined issue, good for newcomerssimple and well-defined issue, good for newcomersservernvisy-server: API handlers, middleware, authnvisy-server: API handlers, middleware, auth