When you end your LoL game share some code please XD

What operation are you trying to do?

cookies and headers are accessible in middleware because this runs before every page request, so it has access to the header and cookies from the client.

You can access cookies and headers in server components too, but they need to become dynamic; cookies, headers (and others) are now async therefore now you need to await them.

not disrupting other people in a game, respect 🤝

when I use next.js next/headers to get cookies from an api route that I call using fetch from the client, I get the value, but when I attempt to get cookies from an api route that I call using fetch from middleware, I don't get the cookies. Am I missing something?

it isn't a server component

it's an actual api route

i.e

export async function POST(request) {
// ... get cookies
}

I'm just trying to read them

I guess it's just weird that they are showing ON THE API ROUTE for a fetch from the client vs a fetch from the middleware

The docs seem to imply that maybe the cookies shouldn't be populated that way AT ALL????

Tell me if I get what is happening:
- (works✅) you tried to read cookies INSIDE an API route, this route.ts gets called by the client

- (❌fails) you tried to read cookies in the SAME API route, but when this route.ts gets called by the middleware it doesn’t work?

yea

exactly

but I tried to read with next/headers rather than request.whatever whatever

Have you tried reading from request.cookies.get("cookie-whatever")?

Also, what happens if you read and cookies in the middleware itself? Does that work?
If that works , maybe try appending the cookies explicitly in the fetch call.

If neither work then I have no idea, and you should go back to LoL to forget about it and I should apologize for wasting your time xd

I have, and reading in the middleware works yes

just trying to understand the why though

it makes no sense xD

Middleware intercepts the request

It might as well reset it or mutate it. what If you read the cookies from the incoming request and then pass them to the route handler explicitly?

It's interesting that in the non-middleware case, request.headers.cookie is empty

or wait

what

this prints the full request object headers

and I see my cookies

but when I do console.log(headers.cookie) it is undefined

😕

makes no sense

I think I'm just in a weird state of undefined behavior

I made the false assumption that next/headers worked on the API side

and it kinda does????...

I can set cookies

but it seems like reading them that way is not okay

so it sounds like I should stop using next/headers in the API routes entirely and then revisit this problem

😆

try this : const requestHeaders = new Headers(request.headers)

and console.log(requestHeaders)