Set (send) cookies server side like in Express.js via ctx.res.cookie

[slava-lu]

Feature request

There is no easy way to send cookies from the server in next.js, You can get cookies via ctx.req.headers.cookie so one would expect to send them via ctx.res.[headers].cookie in getInitialProps similar to express.js

Is it something on your radar? Or can you recommended a third party lib to do that?

[merelinguist]

Try next-cookies

[slava-lu]

Try next-cookies

It only reads cookies but does not send them in http response. This lib has 4 lines of code.

[vassbence]

You can create a simple function for yourself or just use the native node.js implementation.

[slava-lu]

You can create a simple function for yourself or just use the native node.js implementation.

I know that I can create it myself as well as I can do SSR myself. But the question was different.

[vassbence]

In express res.cookie is just a very simple function, as the docs state:

All res.cookie() does is set the HTTP Set-Cookie header with the options provided. Any option not specified defaults to the value stated in RFC 6265.

If you would like to mimic express.js you can just write it, and since this can be solved quite easily in user-land I doubt Next needs to add anything.

Also you mentioned sending cookies in getInitialProps. I'm not sure it's the right place to do, could you describe your use-case?

[slava-lu]

Also you mentioned sending cookies in getInitialProps. I'm not sure it's the right place to do, could you describe your use-case?

the case is quite simple. Imagine a user token expires and I want to delete it or change it when a user goes to the site and renders a page. If I can't modify the token in cookie server side, then I will have to wait till user makes a second request to API from the client to modify the token in cookie.

[vassbence]

If the token is expired they should not be able to get any sensitive info anyways. For example you have a /api/user, the endpoint should send a 40x if the token provided is not good. It can also delete it right away. The only thing you should put in getInitialProps is the fetch for the data, the logic should be handled in the api endpoints, with httpOnly cookies.

[slava-lu]

Ok. Thanks for the hint.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.