Cookies set in middleware missing on server actions about next.js HOT 4 CLOSED

A bit tricky to see the issue in your example, because, straight up navigating to the landing page, sets a cookie too. That being said, I think something like this should work:

import { NextRequest, NextResponse } from "next/server";

export async function middleware(request: NextRequest) {
  const expires = new Date();
  expires.setMinutes(expires.getMinutes() + 60);

  const cookie = {
    httpOnly: true,
    name: "random_string",
    value: Math.random().toString(),
    expires,
  };

  request.cookies.set(cookie.name, cookie.value);

  let response = NextResponse.next({
    request: {
      headers: new Headers(request.headers),
    },
  });
  response.cookies.set(cookie);

  return response;
}

from next.js.

I mean, I put it together from information present in the docs.

• https://nextjs.org/docs/app/building-your-application/routing/middleware#setting-headers

That link documents how to forward modified headers.

And that it is mentioned that you can set cookies on the incoming request:

For incoming requests, cookies comes with the following methods: get, getAll, set, and delete cookies. You can check for the existence of a cookie with has or remove all cookies with clear.

On the same page as the link above.

from next.js.

@icyJoseph It's kind of difficult to reproduce, you have to simulate the "access_token" (random_string) cookie expiring when calling server action, that's why I said to clear the cookies in the first step.

I tested your example and it worked, but is it the right way to do this? Looks like I'm back to the issue #49442

from next.js.

I believe this issue is impacting supabase sever side auth on NextJS supabase/ssr#36

from next.js.