-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[bug]system-proxy exclusion list not used #1312
Comments
There are a number of proxy related bugs in Cypress - basically we aren't respecting or handling proxies and we should. There's nothing wrong with the Chrome network proxy settings - the browser needs to route all traffic through Cypress who then needs to reroute that through your proxy server settings. There are a few workarounds if you search for |
As Brian said, all traffic (even to localhost) should flow through the Cypress proxy. This issue describes Cypress working as designed so I will close it for now. |
Fixed by #3531 |
Released in |
Current behavior:
when testing a self-hosted website (like
localhost:8888
in my case) the requests run trough the cypress proxy. requests not for cypress go trough to the system proxy.Only when we request
localhost:8888
(withcy.visit
) we see the 404 response from our corporate proxy server.The point is that the request shouldn't go TO the proxy server cause the host (
localhost
) is on the system proxy exclusion list.When opening a new tab in the chrome spawned with cypress, we still can't go to
localhost:8888
When opening my own chrome (without the cypress proxy) i CAN navigate to
localhost:8888
.My cypress chrome
chrome://net-internals/#proxy
page says:Effective proxy settings
My normal chrome
chrome://net-internals/#proxy
page says:(where
<local>
andlocalhost/127.0.0.1/::1
etc. are the same)How to reproduce:
configure a system proxy server, and add
localhost
to the exclusion list.Host your website (in
iis
, or via some npm package) on localhost, and usecy.visit
to test it.The text was updated successfully, but these errors were encountered: