Incorrect document.domain

Current behavior:

When running Cypress against a subdomain (e.g. sub.example.com), document.domain is reported as example.com.

Desired behavior:

document.domain should be the full domain name sub.example.com.

Steps to reproduce:

Run a Cypress test against a subdomain:

cy.visit("https://en.m.wikipedia.org/wiki/Main_Page")

Then run document.domain in the dev console. Expected output: "en.m.wikipedia.org".

Versions

Latest Cypress using Chrome Canary.

[jennifer-shehane]

We reviewed this as a team and have decided that while this is unexpected behavior, we won’t be changing this behavior in Cypress today.

With the way Cypress works today, we have to set the document.domain in this way to avoid issues with visiting other subdomains. If this is causing problems within your testing, we suggest updating your application code, so that when visiting during testing, within a testing environment, it removes any limitations around the document.domain issue.

To more directly address @tdelphi, in this case, from the information you provided, we would recommend turning off the OWASP CSRFGuard restrictions during testing.

A simple way to check if your application is running while being visited within Cypress can be found here. I’d suggest a combination of detecting Cypress and also knowing that the tests are being run from within your own development team - then changing the application logic in this instance.

@nicojs I’m not sure about the issue you are encountering exactly, since you never described it, so let us know if there is some limitations to our suggestion.

We’re always welcome to reconsider fixing this or offering a better workaround or errors in the future. So, please comment if you have objections to our suggestion.

[sscaff1]

We have the same situation with a very old application. This is preventing us from using cypress for testing…We were hoping to move from Selenium to Cypress…

Why can’t this be configurable?