A request aborted by the client is logged as an unhandled 500
维护者通常 1 天内回复
还没有人认领这个 Issue。
- #8536 来自 @mixelburg —— 已关闭,未合并
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 75/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- node.js, typescript
调研方向
Start with executeMiddleware in packages/start-server-core/src/createStartHandler.ts around lines 413, 436, and 475, then trace the rejection through requestHandler in packages/start-server-core/src/request-response.ts around lines 121-143. Reproduce the behavior with a delayed loader, a built server, and curl -m 0.2. Done means a client-aborted request ends quietly without the unhandled error log or a server-side 500 response.
由索引模型根据 Issue 内容生成。
描述
What happens
When a client closes the connection while a request is still running, Start prints the abort reason as an unhandled error on the server, with status 500:
Error: aborted
at abortIncoming (node:_http_server:921:17)
... 2 lines matching cause stack trace ...
at TCP.<anonymous> (node:net:362:12) {
cause: Error: aborted
at abortIncoming (node:_http_server:921:17)
at socketOnClose (node:_http_server:914:3)
at Socket.emit (node:events:526:24)
at TCP.<anonymous> (node:net:362:12) {
code: 'ECONNRESET'
},
status: 500,
statusText: undefined,
headers: undefined,
data: undefined,
body: undefined,
unhandled: true
}
Nobody receives the 500, because the client has gone. In production, every user who navigates away while a loader or server function is waiting prints one of these. It cannot be caught from application code. A request middleware that catches the abort and returns its own Response still gets the line, and so does a custom src/server.ts that wraps handler.fetch in a try/catch, because the error never leaves handler.fetch. Start returns a 500 Response and logs it on the way.
Why
- Once
request.signalaborts,executeMiddlewarethrowssignal.reasonwhatever the middleware returned:createStartHandler.tsL413, L436, L475. requestHandlerpasses the rejected promise to h3'stoResponsewith no config:request-response.tsL141.- h3's
prepareResponsetreats anything that is not anHTTPErroras unhandled, logs it withconsole.errorunlessconfig.silentis set, and answers 500.
The reason is whatever the server runtime aborts the signal with. Under srvx it is Node's socket error (Error: aborted, ECONNRESET). An AbortError would be logged the same way, since it is an Error and not an HTTPError.
This is close to #8155, which fixed the SSR render stream surfacing the same abort. That path is fixed in our versions. This one is the middleware runner's throw, which reaches h3 whatever the render does.
Steps
- A route whose loader calls a server function that waits for a few seconds, for example an upstream call with a long deadline.
vite build, then start the built server.curl -m 0.2 http://localhost:3000/<that route>, so the client leaves while the loader waits.- The server prints the error above. In our app the request middleware's own log line records the request as a 499 with
aborted: truejust before it, so the app did see the abort.
Expected
A request the client aborted ends quietly. Two possible shapes: requestHandler answers a bare response without calling h3 when request.signal.aborted and the rejection is request.signal.reason, or it passes h3 an onError that does the same.
Versions
@tanstack/react-start1.168.56 (1.168.58 is the same: it depends on the same server core)@tanstack/start-server-core1.169.37 (latest).mainat3cdd1af04bhas the same code.h3-v2([email protected]), bundled by Startnitro3.0.260903-beta vianitro/vite,srvx1.0.3- Node 24.21.0, macOS
- 主要语言
- TypeScript
- 星标
- 15.3k
- 派生
- 1.9k
- 平均合并
- 1 天 5 小时
- 30 天内合并 PR
- 46
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TanStack/router 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
Masked navigation drops the first character of the hash each time (__tempLocation hash missing '#')可能已有人在做 @hassanabrar202 于 8 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
router-generator: lazy-load Prettier (costs ~300–450ms per build even when formatting is off)可能已有人在做 @Sheraff 于 27 天前认领。 未关闭package: router-generator performance
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
router-generator: sibling `physical()` subtrees in a virtual route config generate duplicate identifiers可能已有人在做 @Sheraff 于 27 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
docs(router): clarify static title fallback in SPA mode可能已有人在做 @Rohan-Dedhia 于 17 天前认领。 未关闭
难度 1/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
相似的 Issue
-
[BUG]: Shared links drop the configured basePath on GitHub Pages可能已有人在做 @anshulchikhale30-p 今天认领。 未关闭bug
难度 1/5 1 小时以内 新手友好度 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 条评论 ·
维护者通常 1 天内回复
-
Add: GTrekker未关闭check:passed streams:add
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
Koenkk/zigbee-herdsman-converters#13900 ·
维护者通常 1 天内回复
-
area: ui Bug Payload OSS
难度 1/5 1 小时以内 新手友好度 88/100
payloadcms/payload#19839 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
jeanibarz/knowledge-base-mcp-server#1291 ·
维护者通常 1 天内回复