Skip to content
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

chromeWebSecurity:false is not working #19435

Closed
varshanharshank opened this issue Dec 21, 2021 · 6 comments
Closed

chromeWebSecurity:false is not working #19435

varshanharshank opened this issue Dec 21, 2021 · 6 comments

Comments

@varshanharshank
Copy link

Current behavior

I had set the attribute chromeWebSecurity:false in cypress.json. But when i execute my test, it is throwing the below error.

Note: In my script, two different urls.

CypressError: cy.visit() failed because you are attempting to visit a URL that is of a different origin.

The new URL is considered a different origin because the following parts of the URL are different:

superdomain

You may only cy.visit() same-origin URLs within a single test.

Desired behavior

It should consider the chromeWebSecurity:false and able to navigate different domains

Test code to reproduce

I am running scripts in BDD style .

Cypress Version

9.1.1

Other

No response

@mjhenkes
Copy link
Member

mjhenkes commented Jan 3, 2022

I believe you're running into our current multi-domain limitation. We're currently working on supporting multi-domain.

Follow #17336 for progress updates.

For more info see our current multi-domain limitation documentation

@sainthkh sainthkh added the stage: awaiting response Potential fix was proposed; awaiting response label Jan 20, 2022
da70 added a commit to NYULibraries/primo-explore-views that referenced this issue Apr 20, 2022
@NorseGaud
Copy link

@mjhenkes, Cypress 11.x is out and this is still an issue.

@cypress-app-bot
Copy link
Collaborator

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

@cypress-app-bot cypress-app-bot added the stale no activity on this issue for a long period label May 22, 2023
@NorseGaud
Copy link

bump

@nagash77 nagash77 removed stage: awaiting response Potential fix was proposed; awaiting response stale no activity on this issue for a long period labels May 23, 2023
@AtofStryker
Copy link
Contributor

@NorseGaud @varshanharshank would either of you be able to provide a reproduction of the issue with the latest version of Cypress?

@AtofStryker
Copy link
Contributor

Unfortunately we have to close this issue due to inactivity. Please comment if there is new information to provide concerning the original issue and we can reopen.

@AtofStryker AtofStryker removed their assignment Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants