Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Setting cookie options
See original GitHub issueUpon pushing to a staging server I get an issue that I did not get at localhost. The cookie saved gives me the following console warning:
Cookie “strapi_jwt” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
How to change the value of SameSite in the cookie?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Please also expose options to set “TOKEN_KEY” name, one might not want to use “strapi_jwt”
Turns out the problem was using nuxt-fontawesome instead of @nuxtjs/fontawesome! I’ve no idea why but making this change solved the issue, at least for me.