Reject oversized request bodies before reading#610
Conversation
Reject incoming requests with Content-Length larger than the 1MB cap before reading the body (BUG-API-01). - Defined `ContentTooLargeError` exception. - Updated `_read_json_body` to raise `ContentTooLargeError` for oversized requests. - Updated `do_POST` to catch `ContentTooLargeError` and return `413 Payload Too Large`. - Added unit tests in `tests/test_reflection_dashboard_api_oversized.py`. Co-authored-by: safal207 <55020240+safal207@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
The Reflection Dashboard API now correctly identifies and rejects requests where the
Content-Lengthexceeds the 1MB limit before attempting to read the body. It returns a semantically correct413 Payload Too Largestatus code. This was achieved by introducing aContentTooLargeErrorexception and updating thedo_POSTerror handling logic. Unit tests have been added to ensure this behavior is maintained.PR created automatically by Jules for task 5255638131345680818 started by @safal207