Increase Express JSON Payload Limit to 10mb and Handle Large Payload Errors#12
Conversation
…oo large errors
- Increased `express.json({ limit: '10mb' })` to support large LLM context requests.
- Added explicit error handling in Express to return a `413 Payload Too Large` JSON response when the body parser throws `entity.too.large`, preventing it from dropping into the generic 500 handler.
- Added a robustness test to verify large payload handling.
Co-authored-by: shenald-dev <245350826+shenald-dev@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. |
The default
express.json()limit is 100kb, which is typically insufficient for large context windows, code bases, or long multi-shot conversations in LLM applications. Furthermore, exceeding this limit throws apayload.too.largeerror, which drops to a generic 500 status rather than providing a structured client-side413code.This patch:
express.jsonlimit to10mb.err.type === 'entity.too.large'and returns a413JSON response.PR created automatically by Jules for task 1456487148125950924 started by @shenald-dev