Is it possible to set a cookie on a serverless function in Next?

[mirshko]

for some reason this isn't creating the cookie?

[maticzav]

Could you show the entire function?

[mirshko]

export default async (req, res) => {
  try {
    const { email, password } = JSON.parse(req.body);

    const session = await login(email, password);

    res.status(200).json(session);
  } catch (err) {
    console.error(err);

    res.status(401).json({
      error: err.message,
    });
  }
};

right now im returning the secret returned from login and then setting it as a cookie on the client.

would probably be safer to not even pass it to the frontend at all, only set / destroy the cookies on the server side

it seems its possible to do

const cookie = serialize(TOKEN_NAME, '', {
    maxAge: -1,
    path: '/',
  })

  res.setHeader('Set-Cookie', cookie)

but this would be a diff workaround.

[mirshko]

@maticzav any help here?

[maticzav]

@mirshko I am sorry, I am not sure I know the answer. Perhaps someone from community could help if they spot the issue.

[leosuncin]

res needs to be wrapped with curly braces

setCookie({ res }, 'token', token, {
  httpOnly: true,
  path: '/',
  sameSite: 'strict',
});

[mirshko]

oh shit! that makes sense as it’s not the whole response context object!

let me test this! thanks!

[andrewmartin]

Hi there, I'm having the exact same issue here. I'm using more or less the exact same sample code. Wrapping in the { req } didn't seem to work.

It's odd because it actually does save it (when I log out the res.cookies I see it). But it doesn't persist in the browser.

const handler = (req: NextApiRequest, res: NextApiResponse) => {
  const { token } = req.body

  nookies.set({ res }, 'fromServer', 'value', {
    maxAge: 30 * 24 * 60 * 60,
    path: '/page',
  })

  // Return the `set-cookie` header so we can display it in the browser and show that it works!
  res.send({
    token: res.getHeader('Set-Cookie'), // strangely, I'm seeing it in the output here!
  })
}

Any thoughts? I'm going to try the suggestion here in the meantime. #249 (comment)

[andrewmartin]

My apologies, I fat-fingered the paste:

path: '/page'

Looks like this is working great. Thanks much and sorry to bug!