Uh oh!
There was an error while loading. Please reload this page.
Enable support for samesite=none - #142
Conversation
literakl
commented
Aug 7, 2020
What is the impact of ignoring this merge request? The time when Chrome will change its behaviour is very close. |
octopicorn
commented
Sep 18, 2020
The impact seems to be that all cookies will be forced to samesite=lax when using Chrome now, since we can't set this property. Is there any reason this is still waiting for merge? |
bernardbaker
commented
Sep 22, 2020
@literakl@CriGoT@octopicorn apologies for being frank. But what's happening with this merge? I'm stuck with the older version which doesn't support SameSite. Leaving me with LAX on my app. Which has a front end in Netlify and the backend Express server on Heroku (cross - domain). |
chris-codaio
commented
Jan 20, 2022
I just ran into this myself trying to build support for hosting our site in an iframe (requiring a SameSite=none cookie). Would love to see this update go through. |
Updates
cookiesto version 0.8.* to enable usingsamesite=nonein preparation for the upcoming change in defaults in Chrome and other browsers ref