Cookie does not support same name with different paths about edge-runtime HOT 3 CLOSED

+1

We want to update a domain of cookie by deleting and recreating it.

This does not work:

  response.cookies.set({
    name: COOKIE_NAME,
    value: '',
    domain: `.${host}`,
    httpOnly: true,
    maxAge: -1,
  });
  response.cookies.set({
    name: COOKIE_NAME,
    value,
    httpOnly: true,
    maxAge: 60 * 60,
  });

There is only a single Set-Cookie header in the response and the last set takes precedence.

This does work:

  response.headers.set(
    'Set-Cookie',
    `${COOKIE_NAME}=; HttpOnly; Max-Age=0; Path=/; Domain=.${host}, ${COOKIE_NAME}=${
      value
    }; HttpOnly; Max-Age=${60 * 60}; Path=/;`,
  );

Note: we are using Next 13.4.3.

EDIT:
This seems to be unrelated to cookies having the same name. For me it is just always the last instruction no matter which names they have.

There is also a related NextJS issue that has been closed but it is actually not fixed: vercel/next.js#38302

I think using the name as a key in this Map causes overwriting cookie instructions for the same name:

from edge-runtime.

@motopods @JannikWempe Can you please reproduce the buggy behavior, pasting a code snippet that can be pasted at DevTools? 🙏

from edge-runtime.

I believe this is fixed by 586de6e; consider commenting if not!

from edge-runtime.