-
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 for cross origin cookie handling for other resource types when experimentalSessionAndOrigin
is enabled
#22952
Labels
topic: cy.origin
Problems or enhancements related to cy.origin command
type: enhancement
Requested enhancement of existing feature
Comments
possibly related to #22882 |
AtofStryker
added
topic: cy.origin
Problems or enhancements related to cy.origin command
type: enhancement
Requested enhancement of existing feature
labels
Jul 27, 2022
2 tasks
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
and removed
stage: routed to e2e-auth
labels
Jul 27, 2022
cypress-bot
bot
added
stage: pending release
and removed
stage: needs review
The PR code is done & tested, needs review
labels
Jul 29, 2022
The code for this is done in cypress-io/cypress#22963, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
topic: cy.origin
Problems or enhancements related to cy.origin command
type: enhancement
Requested enhancement of existing feature
What would you like?
Cypress, when using
experimentalSessionAndOrigin
, only handles cross origin cookies if the request comes from the AUT Frame. This only includes requests made by the Document in the AUT and not XHR or other types of requests that may also need cross origin handling.We would like to see cookie handling applied to other resource types coming from the AUT, likely including
XHR
andFetch
resource types (and possibly others).Why is this needed?
Currently, users are unable to log into Google due to cookie mismatches after signing in. This is due to cookies not being sent with the XHR request. This also should apply the cookie logic more consistently to behave more like the browser.
Other
No response
The text was updated successfully, but these errors were encountered: