[Start] `setResponseStatus` in a server fn called by a loader during SSR becomes the HTML document's status (since 1.169.0) #8834
Send to my agentWhich project does this relate to?#
Start
Describe the bug#
A server fn sets a status for its RPC caller, for example setResponseStatus(503) when an upstream is down, and returns a fallback value (or throws, and the loader catches). When a route loader calls that fn during SSR, the fn runs in the document request's context, and the status it set replaces the document's status. The page renders its fallback correctly but is served as 503.
export const getItem = createServerFn({ method: 'GET' })
.validator((id: string) => id)
.handler(({ data: id }) => {
setResponseStatus(503)
return { ok: false, id }
})
export const Route = createFileRoute('/items/$id')({
loader: ({ params }) => getItem({ data: params.id }),
component: Item,
})
On a client navigation the RPC answers 503, which is what the fn intends. On a full page load, GET /items/1 answers 503 with a fully rendered page.
The same thing happens when the fn throws after setResponseStatus(503) and the loader catches the error. Response headers set by the fn (for example cache-control) also reach the document. That is probably wanted for setCookie, so this report is about the status.
This is a regression. @tanstack/react-start 1.168.60 (start-server-core 1.169.39) answers 200. 1.169.0 (start-server-core 1.169.41, which shipped #7588) and 1.169.4 answer 503.
Complete minimal reproducer#
https://github.com/Tarekkharsa/tanstack-start-server-fn-status
Steps to Reproduce the Bug#
pnpm i && pnpm test- The test builds, runs
vite previewon port 7311, fetches/items/1and/caught/1, then clicks the same routes in Chromium to record the RPC status. It exits 1 when a document is not 200.
Output:
SSR document requests (a route loader calls a server fn that sets 503):
FAIL GET /items/1 -> HTTP 503 (expected 200); fallback rendered: true
FAIL GET /caught/1 -> HTTP 503 (expected 200); fallback rendered: true
Client navigation (the same server fn called as an RPC):
info /items/1: RPC /_serverFn/8804e69444d5c... -> HTTP 503 (503 is intended here)
info /caught/1: RPC /_serverFn/5863b083327b3... -> HTTP 503 (503 is intended here)
2/2 documents answered with the server fn's status instead of 200
Expected behavior#
A status set by a server fn applies to that fn's own RPC response. When a loader calls the fn in-process during SSR, the document keeps the status the router decides (200 here, or 404 from notFound(), and so on).
Screenshots or Videos#
n/a
Platform#
- Router / Start Version:
@tanstack/react-start1.169.4,@tanstack/start-server-core1.169.45,@tanstack/react-router1.170.46,@tanstack/router-core1.171.39 - React: 19.3.1
- OS: macOS 27.0
- Node: 24.22.1
- Browser: Chromium 156 (Playwright 1.64.1), only for the RPC half of the test
- Bundler: vite
- Bundler Version: 8.3.5
Additional context#
Where it happens, in the published @tanstack/start-server-core@1.169.45 dist/esm:
internal-request-response.js:449-453: oneeventper incoming request, run witheventStorage.run(event, ...).internal-request-response.js:715-726:setResponseStatuswritesgetResponseState(event).statuson that event.createSsrRpc.js:8: during SSR the fn runs in-process throughgetServerFnById(id, { origin: 'server' }), inside the same event.createStartHandler.js:500: the document goes throughfinalizeResponse(response, event), andapplyResponseState(internal-request-response.js:255-279) sendshelperStatus ?? response.status.
So the fn's status lands on the document. The RPC path reads the same state through getSerializedResponseState() (server-functions-handler.js:331), which is the intended use.
Possible fixes:
When a server fn runs in-process (origin
server, not a server-fn request), saveresponseState.status/statusTextbefore the call and restore them after. Headers and cookies still merge into the document as they do now.Or give the fn's handler and function middleware a public way to know whether it runs as an RPC. Today an app can only check internals (
x-tsr-serverFnheader plusTSS_SERVER_FN_BASE), or passhandlerTypefrom a request middleware through context:const handlerTypeMiddleware = createMiddleware().server(({ next, handlerType }) => next({ context: { isServerFnRpc: handlerType === 'serverFn' } }), ) export const startInstance = createStart(() => ({ requestMiddleware: [handlerTypeMiddleware] })) // in the fn: if (context.isServerFnRpc) setResponseStatus(503)I checked this workaround against the reproducer: documents answer 200 and the RPCs still answer 503.
Related, not duplicates:
- #7588: response reconciliation, the change that made helper state override the returned response.
- #6785 (open PR): keeps the status when a handler throws after
setResponseStatus. - #7647 (open): keeping a middleware-set status drops middleware-set headers.
- #7914 (open): response-context headers in non-2xx serialized server fn responses.
- #5107, #5407 (closed):
setResponseStatusignored withthrowand in global middleware.
This issue was drafted with an AI assistant and checked by me against the reproducer.
Thanks, that makes sense: the response helpers write to the request's response, and an in-process call during SSR shares it.
Then I'd like to turn this into the feature. Start already knows the caller:
server-functions-handlerlooks the fn up with{ origin: "client" }andcreateSsrRpcwith{ origin: "server" }, but the handler and function middleware never see it. A sketch: pass it through to their context:export const getItem = createServerFn({ method: "GET" }) .handler(({ origin }) => { if (origin === "client") setResponseStatus(503) return { ok: false } })If that shape works for you, I can open a PR with tests, and retitle this issue as a feature request. Should the field follow the internal name
origin, or something more explicit?Ah right, that's what I ended up using for the workaround: a request middleware reads
handlerTypeand passes it down throughcontext, and the fn only sets the status when it's'serverFn'. With that, the documents in the repro come back 200 and the RPC calls still get their 503.The one thing I noticed is that it's only on the request middleware options, so function middleware and the handler don't see it unless you thread it through context yourself.
Sign in to join this conversation.
this is the intended behavior. any
setResponseStatus/ response header setting etc. will also influence the document response."Or give the fn's handler and function middleware a public way to know whether it runs as an RPC." seems viable