fix(guard, runner): enforce http body size and ws msg size#4252
Conversation
|
🚅 Deployed to the rivet-pr-4252 environment in rivet-frontend
|
PR Review: fix(guard, runner): enforce http body size and ws msg sizeGood direction — enforcing size limits at the guard layer is the right architectural approach. A few issues to address before merging. Bug: Unused import (compile warning / dead code)In use rivet_guard_core::proxy_service::MAX_BODY_SIZE;This import is never used. The size check at line 791 uses Required documentation updateCLAUDE.md requires: "When changing actor/runtime limits or behavior that affects documented limits (for example KV, queue, SQLite, WebSocket, HTTP, or timeouts), update
Orphaned error artifact
Status code semantics: 413 for all
|
855bbaa to
889a15b
Compare
| "code": "invalid_response_body", | ||
| "group": "guard", | ||
| "message": "Unable to parse response body." | ||
| } No newline at end of file |
There was a problem hiding this comment.
Add a newline at the end of the file to fix the 'No newline at end of file' linting error
Spotted by Graphite Agent (based on CI logs)
Is this helpful? React 👍 or 👎 to let us know.
889a15b to
e89cab8
Compare
ce7323c to
30accfe
Compare
e89cab8 to
a7065e4
Compare
0bb287d to
9c03cf4
Compare
a7065e4 to
6df70f8
Compare
6df70f8 to
350c871
Compare
9c03cf4 to
209ff35
Compare

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:
Fixes RVT-5967