1.97 Server fn headers are incomplete on initial load

[dotnize]

Which project does this relate to?

Start

Describe the bug

In Start 1.97, request headers and cookies from helper functions in @tanstack/start/server or vinxi/http (e.g. getWebRequest) are initially incomplete in server functions called in loaders/beforeLoad, breaking auth stuff.

When navigating/loading another page which will re-trigger beforeLoad, getWebRequest() returns the complete headers.

Your Example Website or App

https://github.com/dotnize/tss-webrequest-server-fn

https://tss-webrequest-server-fn.vercel.app/

Steps to Reproduce the Bug or Issue

1. Clone repo and run dev
2. Load any page. Headers returned and logged from server fn loader will be incomplete.
3. Navigate to /test or /. Complete headers are now returned.

This is reproducible in dev and build.

Expected behavior

Complete headers are always returned by getWebRequest in 1.95.x

Screenshots or Videos

Screencast.From.2025-01-15.16-54-05.mp4

Platform

• OS: [Linux]
• Browser: [Chrome, Firefox]

Additional context

No response

[tannerlinsley]

I have an inkling of why this is happening. I’ll look into it today.

[einarno]

For anyone depending on this 1.95.7 is the last version without this issue

[noah-wardlow]

seeing this too, but also on getHeaders() function. will also note 1.95.7 works as expected

[timoconnellaus]

I can't seem to get this on any version including 1.95.7. I cloned the test repo above and I see the issue with 1.95.7 and 1.97.3 (latest)

[prateekkumarweb]

Not just headers, even getCookies() returns undefined.

[tannerlinsley]

Cookies are powered by headers on the server. So that makes sense. I’m working on it!

[michaeldahl7]

I can't seem to get this on any version including 1.95.7. I cloned the test repo above and I see the issue with 1.95.7 and 1.97.3 (latest)

Make sure your package json doesn't have the ^ in front of the version number. If tanstack/start is ^1.95.7 it would update to 1.97.x due to the ^.

[salamaashoush]

@tannerlinsley any update for this one, it prevents us from using the new React 19 and streaming stuff :D, let me know if I can help in any way