Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
While running a nuxt application on Cloudflare workers. I noticed that no cookies were being found server side.
Inside the
useCookie
composable that comes with nuxt there is some logic to check if the cookie has expired:https://github.com/nuxt/nuxt/blob/41cdaf670247004eab95395910b4a59e87e38bd9/packages/nuxt/src/app/composables/cookie.ts#L46-L55
When defining a store like this:
The date was considered to be the global context, which Cloudflare says will return 1970-01-01.
As a solution in the limitations, I have proposed to use
maxAge
instead ofexpires
.Additional Info
This is hard to reproduce on Stackblitz as this code needs to be running on a Cloudflare worker. You can set up something basic like the above and notice that the cookie will always e expired on the worker server side.