Skip to content

Conversation

@schiller-manuel
Copy link
Contributor

@schiller-manuel schiller-manuel commented Oct 13, 2025

for POST requests, 'close' on req is emitted when the HTTP message has been fully received, NOT when the connection closed

fixes TanStack/router#4271

for POST requests, 'close' on req is emitted when the HTTP message has been fully received, NOT when the connection closed
@codecov
Copy link

codecov bot commented Oct 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@pi0
Copy link
Member

pi0 commented Oct 14, 2025

I have added better tests to show current Bun/Deno/Node behavior: #123 -- currently, Node (HTTP1/HTTP2) and Deno behavior are consistent.

As a result of this PR, we would be introducing a new inconsistency that the Node.js adapter (only in HTTP1 mode) emits fewer (13 => 6) abort events and in HTTP2 mode, behaves same.

@pi0 pi0 changed the title fix: trigger abort signal only upon connection close, not upon req close fix(node): trigger abort signal when body read is done Oct 14, 2025
@pi0 pi0 merged commit 60c002f into h3js:main Oct 14, 2025
3 checks passed
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.

POST serverFn instantly aborts with signal

2 participants