fix: prevent uncaught exception from malformed multipart requests #595
+184
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #594
This PR prevents uncaught exceptions that could crash the Node.js process when malformed multipart requests are received after an async operation in the request handler.
Problem
When
req.file(),req.files(), orreq.parts()is called after any async operation (e.g.,await someOperation()), malformed multipart requests cause an uncaught exception that crashes the process. This happens because:Solution
Added an immediate error listener to file streams in the
onFilehandler that:Changes
Testing
Following TDD principles:
The server now handles malformed requests gracefully with a 400 response instead of crashing.
🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com