Support proxies and improve proxy performance #1469
Comments
setting the environment variables was very helpful for the npm install on Mac. thx for workaround |
Tried setting env using |
Tried do this:
With electron too, added rules in extension, add extension with VPN, added proxy settings in chrome...
|
I've read everything I can find on this issue and tried every suggested workaround but Cypress still cannot connect to websites through our corporate proxy. When will this feature be implemented? It is a massive blocker for any possibility of adoption within our team. |
@Rende11 See this comment regarding |
Did you try to set the corporate proxy into |
The code for this is done in cypress-io/cypress#3531, but has yet to be released. |
Great to hear this is now pending release! I've recently started piloting Cypress at work with the goal of wider adoption and the speed issues we've been facing as a result of corporate proxy issues are the only thing currently holding us back. Any idea when this might be released? |
@rjd40 Soon. We have been working on the release - had to pause to fix some potential regressions in the pre-release. |
@jennifer-shehane Thanks for all the hard work on this, I have a quick question will this proxy improvement also include authentication for proxy? We have that use case since our corporate proxies require authentication with username and password. |
@RicardoVaranda Yes, |
Released in |
Cannot believe that setting a proxy can be this difficult :( - I have a corporate PAC file for a proxy and I tried setting the HTTP and HTTPS proxies through command prompt, nothing seems to work. Agreed, I am not a developer, but the complexity might turn away many testers from setting up Cypress. |
@sriram04144 Have you checked the proxy configuration docs? It explains how to work if all you have is a PAC file. You just need to set https://docs.cypress.io/guides/references/proxy-configuration.html |
This issue will be closed to further comment as the exact issue here was resolved and tested. If you're experiencing a bug similar to this in Cypress or want enhanced functionality for Proxy support, please open a new issue with a fully reproducible example that we can run or explaining the feature you would like. |
Problem
There are several users with corporate proxy issues that are faced at several layers of interacting with Cypress including during:
(a checkmark indicates that a fix is in #3531)
cy.visit()
npm install
cypress verify
(maybe?)baseUrl
is runningThings that won't be fixed as part of this issue
NODE_EXTRA_CA_CERTS
not being used in cy downloadCurrent workarounds:
Setting environment variables
Note: these are NOT cypress environment variables, but system/shell environment variables
Set
HTTP_PROXY
and/orHTTPS_PROXY
to your corporate proxySet
NO_PROXY
forlocalhost
to prevent it from hitting corporate proxyOther workarounds
For
cy.visit()
For Download
CYPRESS_BINARY_VERSION
.For accessing 'Runs' tab in Test Runner
The text was updated successfully, but these errors were encountered: