-
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
Option for using the exact domain when setting a Cookie #16856
Comments
@jennifer-shehane Is this something you consider adding? Can I somehow help with implementing this feature? |
Hi ... Is there any workaround that we can use until this is fixed? |
@Donaab , I found that using |
Are there any updates on this? or a workaround? |
@Songyu-Wang hi there, you said document.cookie could be used as a workaround. would you mind giving an example of how to do that? I am having the same issue as everyone else with Cypress adding a "." in the beginning of my cookie domain. :( |
Hi @Kazathur92, you can find more information about the document.cookie api at the following link: https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
What would you like?
An additional option within
SetCookieOptions
forcy.setCookie(name, value, options)
that allows for setting an exact domain without a prepended period as described in #1896 .Why is this needed?
When setting a cookie for a particular name/domain, if a cookie without a prepended period already exists in the browser then a second cookie with the same name will be created. This results in the browser having two cookies with the same name when the web application only expects one.
The text was updated successfully, but these errors were encountered: