Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

{ "chromeWebSecurity": false } seems not work as expected

See original GitHub issue

Operating System: Linux (ubuntu)
Cypress Version: 0.20.3
Browser Version: Chrome 61

Is this a Feature or Bug?

Bug

Current behavior:

test isn’t successful

Desired behavior:

visit “https://www.springermedizin.de” click “login” (https://signon.springer.com/) title should include “Login”

test should be successful

How to reproduce:

run the test

Test code:


{
"pageLoadTimeout": 200000,
"chromeWebSecurity": false
}


describe('SpringerMedizin Spec', function(){

    it('Login and Logout should work as expected', function(){

        cy.visit('https://www.springermedizin.de');

        cy.get('a.personalisation__login').click();

        cy.title().should('include', 'Login');

    });
});

Additional Info (images, stack traces, etc)

CypressError: Timed out retrying: expected '' to include 'Login'

Issue Analytics

State:
Created 6 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

30reactions

WilliamMayo11commented, Mar 27, 2018

@SteveBrandt @jennifer-shehane

{“chromeWebSecurity”: false} does not work for me either. Are there other tricks to getting this to bypass Cypress’ cross-origin restriction? This is the only conversation I’ve found online about it.

Chrome console displays "refused to display “https://…” in a frame because it set ‘X-Frame-Options’ to ‘sameorigin’.

I’m testing an app that does a lot of cross-origin navigation, and turning off web security in necessary for me. I can’t seem to get past this error, and any help would be very appreciated!

11reactions

RileyDavidson-Evanscommented, Jul 3, 2018

Unfortunately looking through their documentation and the number of open issues this seems to be a seriously and seemingly permanent blocker to using Cyprus for legitimate testing. It’s too bad that a blocker like this just stops its usability dead in its tracks…

Our app uses a Stripe payment iframe, we cannot target and change the input value because of the security issues, so now Cyprus cannot test our actual user workflows which renders it relatively useless unfortunately.

Top Results From Across the Web

Web Security - Cypress Documentation

Set chromeWebSecurity to false Setting chromeWebSecurity to false in Chrome-based browsers allows you to do the following: Display insecure content. Navigate ...

Disable Chrome Web Security for Cypress Testing

While it is possible to change the Cypress config object during a test by using. Cypress.config("chromeWebSecurity", false).

cypress-io/cypress - Gitter

hi! I'm trying to run tests with localhost:3030 url and it is showing a blank page, I've tried even with cy.visit('https://www.google.com ...

How to write end-to-end tests with Cypress and Node.js

In the root of your project, run the following commands: ... fail if we didn't add "chromeWebSecurity": false in our cypress.json config.

Web Security - Cypress - w3resource

Setting chromeWebSecurity to false in Chrome-based browsers enables you to do the following: Display an insecure content; Navigate to any ...