Skip to content

Conversation

@emmanuelthome
Copy link
Contributor

When we see an end marker in a multipart message, the state machine directly classifies the next stream event as EPILOGUE (or PART), which prohibits leaving a byte unused.

fixes #3077

Added test: test_parse_form_post_data_trailing_CR

emmanuelthome and others added 2 commits December 10, 2025 00:10
When we see an end marker in a multipart message, the state machine
directly classifies the next stream event as EPILOGUE (or PART), which
prohibits leaving a byte unused.
@pgjones
Copy link
Member

pgjones commented Dec 23, 2025

I think #3081 is the correct fix for this.

@davidism davidism closed this Jan 2, 2026
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

multipart/form-data parsing appears to truncate a file part by 1 byte

3 participants