blacklistHosts configuration not working with chrome

[sravan-s]

• Operating System: mac os 10.13.2
• Cypress Version: 1.4.1
• Browser Version: Chrome 63

Is this a Feature or Bug?

Bug

Current behaviour:

https://docs.cypress.io/guides/references/configuration.html#blacklistHosts
blacklistHosts works well with Electron but isn't working with chrome.
i.e. - wouldn't block desired websites if we are using chrome for testing

Desired behavior:

blacklistHosts should work well with all browsers

How to reproduce:

• Clone example recipes- https://github.com/cypress-io/cypress-example-recipes
• Run npm run cypress:open and select stubbing-spying__google-analytics
• Set browser as chrome
• Run tests
• Tests should fail

Test code:

Additional Info (images, stack traces, etc)

[brian-mann]

This is a known issue that we just haven't had time to fix yet. I wrote these tests and they could be better. However, this has nothing to do with blacklistHosts - they work just fine. We have a boat load of tests around them. This is failing due to a different issue.

[brian-mann]

Closing because this is an issue with the recipes, not Cypress itself.

cypress-io/cypress-example-recipes#88

[brian-mann]

After investigating it does appear that blacklistHosts are not working under specific conditions that need investigation. I can see via the logs that when running locally it is applying, but under 3 different CI providers it is not. It could be an issue with Cypress itself.

[sravan-s]

One more pointer, blacklist hosts work with chrome on cypress 1.2.0(we found it out recently)

[brian-mann]

I figured out the root cause and will post back here with more information shortly.

[brian-mann]

The root cause of this has to do with browser caching to disk.

What's happening in the Recipes is that because we utilize the same Cypress profile in between runs - that a previous test was first causing a request to https://www.google-analytics.com/analytics.js.

Then the browser would then cache the response to disk.

In subsequent runs of the browser, the Cache had not expired yet - so instead of making a real HTTP request to the server (which would have been blacklisted), the browser serves the file immediately from the disk cache.

We're going to be updating Cypress to automatically clear the disk cache whenever the browser is first spawned.

The related issue is here: #1124

[bahmutov]

Unbelievable find, great work!

…

Sent from my iPhone

On Feb 13, 2018, at 23:52, Brian Mann ***@***.***> wrote: The root cause of this has to do with browser caching to disk. What's happening in the Recipes is that because we utilize the same Cypress profile in between runs - that a previous test was first causing a request to https://www.google-analytics.com/analytics.js. Then the browser would then cache the response to disk. In subsequent runs of the browser, the Cache had not expired yet - so instead of making a real HTTP request to the server (which would have been blacklisted), the browser serves the file immediately from the disk cache. We're going to be updating Cypress to automatically clear the disk cache whenever the browser is first spawned. The related issue is here: #1124 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[brian-mann]

Fixed by #1310

[brian-mann]

Released in 2.0.0.