fix: harden web API runtime controls
This commit is contained in:
@@ -32,3 +32,8 @@
|
||||
- User-caused provider failures are terminal for that request.
|
||||
- Balance or quota exhaustion removes a key from active rotation.
|
||||
- Provider-key state transitions must be audited.
|
||||
|
||||
## Web session posture
|
||||
- Browser sessions use `Secure`, `HttpOnly`, `SameSite=Strict` cookies.
|
||||
- State-changing cookie-authenticated endpoints accept requests only from the configured app/admin origins and require browser `Origin` or `Referer` metadata.
|
||||
- The current API posture assumes a same-origin browser client. If cross-site embeds or third-party POST flows are introduced later, add an explicit CSRF token mechanism instead of relaxing the cookie/origin checks.
|
||||
|
||||
Reference in New Issue
Block a user