-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Cypress cannot load pages behind a corporate proxy #672
Copy link
Copy link
Closed
Labels
pkg/https-proxyThis is due to an issue in the packages/https-proxy directoryThis is due to an issue in the packages/https-proxy directorypkg/serverThis is due to an issue in the packages/server directoryThis is due to an issue in the packages/server directorytopic: 😳 whoops there is no test to runError msg: "Whoops there is no test to run"Error msg: "Whoops there is no test to run"type: question
Description
Activity
Metadata
Metadata
Assignees
Labels
pkg/https-proxyThis is due to an issue in the packages/https-proxy directoryThis is due to an issue in the packages/https-proxy directorypkg/serverThis is due to an issue in the packages/server directoryThis is due to an issue in the packages/server directorytopic: 😳 whoops there is no test to runError msg: "Whoops there is no test to run"Error msg: "Whoops there is no test to run"type: question
Is this a Feature or Bug?
Feature
Current behavior:
When running on a machine that requires a corporate proxy, cypress does not use the proxy settings and therefore cannot access and run tests on pages behind the proxy.
Desired behavior:
Cypress should respect the internal proxy settings of the network. From Brian Mann in Gitter:
"right i think its something we'll have to take into account and upgrade
cypress does not respect the internal proxy settings of the network
it would just work if we took that into account though"
Additional Info (images, stack traces, etc)
Resolving this would allow teams behind corporate proxies to adopt the software.