-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow sameSite in setCookie #2437
Comments
Where do you see the options: docs, typescript, code? |
@bahmutov in the code of cypress...
|
https://docs.adobe.com/content/help/en/target/using/implement-target/before-implement/privacy/google-chrome-samesite-cookie-policies.html |
Is there any progress/update on this feature? The newest version of Chrome requires |
I'm also looking for this feature to be added. We have an app that requires |
This can be added as soon as the code is done. @jm-hmbk @katiejduane @karenpetrie If you'd like to open a PR to speed things up, this should be a small change. @gregorybleiker has identified one of the areas that will need to be updated, and tests will need to be added in the Reading SameSite status is a breaking change that will need to wait for 5.0: #5070 |
@flotwig what do you mean when you say 'this can be added as soon as the code is done'? are you meaning once 5.0 is finished, one could theoretically make the change and make a PR? or are you referring to some other code? Sorry, just need a clarification! Thanks! |
@katiejduane Once there is a PR merged that adds support for Adding it to |
thanks for the quick response @flotwig ...so in order to do this i'd essentially have to clone the repo, make the required changes (ONLY for |
@katiejduane yup, that's right! |
@flotwig sorry to keep bothering you with questions but i saw that issue #6757 was assigned to you. does this mean you'll make the fix or should i still do my best to fix and make a PR? happy to try, just wanted to know if I don't need to. Electron is now also failing due to the cookie being blocked, so we can't get authorized at all right now using |
@katiejduane good eye, i'll probably add a fix for this issue as part of #6757 anyways so don't worry about it for now |
Just came here to figure out this issue - will eagerly await #6757 as well! |
thanks @flotwig , we're essentially blocked right now (except in CI) because our application is in development, and the auth page is at a deployed URL, but the app is still sitting on localhost:3000, so a UI login is out of the question; and so can't run the tests at all. if you think there's a chance you won't have a fix for this with #6757 please let me know and i'll give it my best shot and make a PR. i'd already started making some adjustments before your most recent comments, but obviously am far, far less familiar with this code base than you are. sorry for all my own super verbose comments! 😬 |
thank you @flotwig !!! 😁 |
The code for this is done in cypress-io/cypress#6828, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior:
setCookie has the options "domain", "name", "value", "path", "secure", "httpOnly", "expiry"
Desired behavior:
setCookie should also allow setting the "sameSite" option
Versions
Cypress 3.1.0
sameSite is described in https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie
The text was updated successfully, but these errors were encountered: