Skip to content

fix: don't hang when an epilogue arrives after the closing boundary - #230

Open
official-burak wants to merge 1 commit into
fastify:mainfrom
official-burak:fix-epilogue-finish-hang
Open

official-burak wants to merge 1 commit into
fastify:mainfrom
official-burak:fix-epilogue-finish-hang

Conversation

@official-burak

@official-burak official-burak commented Sep 8, 2026 •

Copy link
Copy Markdown

Thanks for the clear repro on #228. After Dicer sees --boundary-- it gets destroyed, so a later write of the RFC 2046 epilogue never invokes the stream callback and finish never fires.

This ignores writes once the parser is no longer writable and adds a test for the split-chunk case. Same-chunk trailers already worked.

Fixes #228

After Dicer sees the closing delimiter it is destroyed, so a later
write of RFC 2046 epilogue never invokes the stream callback and
finish never fires. Ignore those writes once the parser is closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

finish is never emitted when bytes arrive after the closing boundary in a separate write

2 participants